@alexhall Moving off of mastodon.social and onto your own instance isn't a bad idea. I'd suggest GoToSocial rather than actual Mastodon for a small instance though.

@alexhall I've been thinking about moving to a self-hosted GoToSocial instance myself. Mine would be on a little single-board computer in my apartment that's already set up as a public server, on AT&T fiber with a static IP address.

@dominic @matt Ideally, it would run as a Docker container on my home server, but I'd need to sort out isolation from the rest of the network.

@dominic @alexhall I'm not sure I would use Docker at all for GoToSocial. It's already a single statically linked binary, so I'd just drop that on the VPS and configure Caddy, or nginx or Apache or whatever you're running on your existing server, to reverse-proxy it.

@matt @dominic Oh, that's handy. I assumed it had dependencies and components that all had to be set up. Is the database even included, or does the server need Postgres?

@alexhall @dominic You can use SQLite.

@alexhall @matt thanks for your reply. So you don't use any solution that can makes things more easy to deal with Docker containers ? I'm new about Docker. I've just started to read docs about it 🙂 I seen some interesting solutions like Coolify, CapRover, etc.

@dominic @matt We use Docker at work, so I'm used to handling the basics with the command line. I much prefer docker compose to straight docker.