# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 4
# self = https://watcher.sour.is/conv/ku2sgda
@bender Is it so maxed out you couldn't fit a pretty small program like Headscale on it? Headscale by itself and only personal home type use as far as amount of peers go, it really isn't noticeable I don't think resource-wise. The Docker version I guess could be a different story.
@eldersnake It's only the Docker engine itself that consume a bit more memory which is responsible for managing containers on the host. There's also a tiny bit of overhead with containerd too. which acts as the parent and supervisor of the container, but that's pretty small.
@eldersnake It's only the Docker engine itself that consume a bit more memory which is responsible for managing containers on the host. There's also a tiny bit of overhead with containerd too. which acts as the parent and supervisor of the container, but that's pretty small.
@prologic Good to know. I must admit I've never actually used a Docker instance, probably as I just assumed the overhead might be a bit much for my usual very modest servers.