I host forgejo internally and use that to sync changes. .env and data directories are in .gitignore (they get backed up via a separate process)
All the files are part of my docker group so anyone in it can read everything. Restarting services is handled by systemd unit files (so sudo systemctl stop/start/restart) any user that needs to manipulate containers would have the appropriate sudo access.
It's only me they does all this though, I set it up this way for funsies.
Yep. My instance just has me on it and posting elsewhere works without issue. Anything I upload goes to my instance and federates out. It's really quite great not having to worry about the instance drama when big ones defederate from each other. I also turned off NSFW so I don't have to worry about any of that content (legal or otherwise) even hitting my server.
Here's an image of me making this comment via Sync for Lemmy
Edit: I have community creation locked down to admins, which everything disables them on my instance.
Same
Device information
Sync version: v23.08.12-23:05
Sync flavor: googlePlay
Ultra user: true
View type: Slides
Push enabled: false
Device: panther
Model: Google Pixel 7
Android: 13
There's an outside chance they just don't want to show their username, but yeah OP should make sure they're properly pathing to their creds
I've been running it behind Cloudflare with no issues. I'm also doing it a completely different way than the official docs and the ubergeek method. Mostly because I have a particular way I do my docker stuff.
Every time something has broken it's been 100% on me. My favorite way to learn is by breaking things though, so I also have an account on a different instance in case I break mine and have to wait a bit to fix it 😅
As someone else already said, automated backups should be up on the priority list.
But also maybe try out self hosting Lemmy. It's been a fun little journey and helped me flesh out my Caddy config more than I thought possible.
Agreed. I haven't come across any instances I care to participate in that have that enabled though.
This is ultimately why I decided to roll my own instance. I'm keeping my backup here though in case I mess something up, but full control is nice to have.
It took a little bit of work but I rolled my own docker compose and it's been pretty solid. I pin the specific nextcloud version in my compose file (I don't like using :latest for things) and updating is as simple as incrementing the version, pulling the new image, and restarting the container. I've been running this way for a couple years now and I couldn't be happier with it.