If you're looking to host your very own single-user/a-few-users #fediverse instance, you cannot go wrong with #snac. It is simple to install on Ubuntu and works very well with some really solid clients. It is also written in C, so it is fast, with few dependencies. Great work @grunfink, you've got a new monthly supporter on Ko-fi!
snac is the reason I joined the Fediverse in the first place. This is the only server software I know that tries to mitigate the addiction mechanisms common to most micro-blogging platforms.
@chema@grunfink Endorse. I haven't installed it yet but as a fellow portable C enthusiast I checked it out and did a test compile. No complaints, looks great, including the man pages.
@chema@grunfink Just got this working inside a FreeBSD jail on my LAN. It took rather longer than I imagined, as some of the instructions were misleading, and nginx was being pissy about wanting a full Let'sEncrypt cert chain rather than just the leaf. But I got it up.
The rc.d script examples/snac_freebsd needs to be modified before use, changing SNAC_DATA_PATH to the location of snac2's data (which is later established as /home/snac/data).
pw useradd snac -s /bin/sh is insufficient -- it doesn't create the user's homedir. This should be:
@gyptazy@chema@grunfink 2/n: examples/nginx-alpine-ssl/default.conf needs to be modified before use. The proxy_pass fields need to be modified to point to the local snac port, which was earlier established as localhost:8001.
Further, nginx does not scan any .d subdirectories for configuration files out of the box. In nginx.conf, in the server block, you must add a directive to the effect of:
@gyptazy@chema@grunfink 3/n: The HOWTO establishes different hostnames when setting up snac versus nginx (snac01.gyptazy.ch versus snac.gyptazy.ch), but doesn't explain why this was done. Indeed, this seems like a thing to not do, as snac uses the hostname you give it to generate URLs to itself.
@gyptazy@chema@grunfink 4/n: I'm not using certbot for my Let's Encrypt certs, because I have a cert with a wildcard SAN, my DNS provider doen't support API access to update TXT records, so I get to do it all by hand. Every three months.
A brief note to the effect that nginx wants the entire cert chain, not just the leaf cert, would be welcome.
...Oh, not sure why you version-pinned certbot at 2.6 in the pkg install. FreeBSD 13.2 is on cerbot 2.9.
Add comment