# 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 5
# self = https://watcher.sour.is/conv/erbrtyq
@prologic I thought you were one of the people telling me how great it was. It is a Go project, after all. What do you usually use? I always find myself spending a lot of time making Nginx do what I want and I don't think I've ever had automatic certificate renewal work the first time.
Caddy just works. I have some self-hosted Web services with easy-to-remember subdomains that only exist on my Wireguard network with a valid Let's Encrypt (wildcard) certificate so browsers don't complain. It *should* be automatically renewed without my input but we'll see what happens. It took shockingly little effort, even considering I need to customize the Docker image and create API keys so it can solve a DNS challenge using my provider.
I'm still not thrilled about using software that does magic for you (like Docker and Caddy) but it sure makes things easy.
@mckinley Nah it wasn't me, trust me 🤣 I _actually_ use Traefik for my ingres.
@mckinley Nah it wasn't me, trust me 🤣 I _actually_ use Traefik for my ingres.
@prologic Ah yes, the other Go reverse proxy. Caddy seems simpler to me, more like Nginx with better defaults and a built-in ACME client. Traefik seems to have way more bells and whistles for all kinds of crazy setups when I only need to map domain names to containername:port pairs.
@mckinley Caddy is simpler and act as both, web server *and* a reverse proxy. Traefik is only—albeit on steroids—a reverse proxy.