• 4 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • Cool guide, I’ll keep it in mind when setting up my own Lemmy, even though I won’t go through cloudflare. Some things I noticed:

    • Since I didn’t see you mentioning it, ufw (idk about gufw) doesn’t actually block the ports opened by docker. Make sure to only forward your docker ports to localhost and only make the actual webservice available (e.g. 127.0.0.1:8888:8080 for piefed adminer), otherwise the ports will be accessible from your LAN
    • In your update process, you can docker compose pull before docker compose down, makes a little difference especially on a slow connection/big images. I think you don’t even need the down command since docker does that automatically if something changes (e.g. new build)





  • If you’re selfhosting already, you know how to deploy it. Are those services available in the internet via some domain? Having an SSL certificate with automated renewal is quite important. Make sure to update the machine the service runs on regular.

    Backups! Having daily snapshots to be able to roll back if necessary is great. If you want to use your own hardware, I suggest Proxmox. If you want to rent a VPS, see if the cloud provider has something like that as well (will likely cost a little extra). Also, check the service’s documentation on what data to back to in order to be able to restore on a new machine in case your server explodes. (3-2-1 rule). Shutting down the instance with no prior warning because of some error you can’t recover from because of no working backup is the best way to spoil anyone’s experience.

    If you use docker, make sure to have it behind a reverse proxy and configure your docker ports to be bound to localhost only so you don’t accidentally expose your database to the internet.

    Think not only about technical deployment but also governance. Set instance rules and think how you want to do moderation. See if you have someone to help you with that.

    Go for it! Set it up, fiddle around for a while and when you get comfortable, invite your friends. Just be upfront that there might be an occasional downtime for maintenance (which you will advertise a day before or so) every now and then.





  • The resources required by federating depend on how many people follow each other across those two instances and how much these post. Just existing and theoretically federating doesn’t need any resources if there’s nobody following, assuming threads isn’t doing that different from everyone else.

    For each post a user makes on your instance, it sends that post to each instance where someone follows the poster. There’s no automatic sending to every known instance of every post on your instance.