

It’s the type of crowd that self hosting brings. We’re very much more Lemmings than Redditors by trade, so it does make sense the community here is better.
That, and fuck reddit.


It’s the type of crowd that self hosting brings. We’re very much more Lemmings than Redditors by trade, so it does make sense the community here is better.
That, and fuck reddit.


If anybody uses this in prod from a git repo, might want to place your database creds in an .env file adjacent to your compose file then gitignore the .env.
Referenced like so:
.env contents
MYSQL_ROOT_PASSWORD=MyExamplePassword
MYSQL_ROOT_USER=MyExampleUser
docker-compose.yml contents:
MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
MYSQL_ROOT_USER: ${MYSQL_ROOT_USER}
Don’t commit secrets to git!
Damn mobile formatting.


Sensible consumer. Why weren’t there more of you when I was working retail?


Honestly the single biggest thing to self-hosting is breaking stuff.
Host stuff that seems interesting to you, and dick around with it. If it breaks, read the logs and try to fix. If you can’t, revert to a backup and try to reproduce.
If you start out with things that interest you, you’ll more likely stick with the hobby. From there you can move to hosting things with external access - maybe vpn inside your own network through your router?
From there, get your security in line and host a basic webserver. Something small, low attack vector, and build on it. Then expand!
Definitely recommend docker to start with - specifically docker compose. Read the documentation and mess around!
First container I would host is portainer. General web admin/management panel for containers.
Good luck :).
Quickly read through the writeup, excellent work. I’ve been meaning to do something similar to this but haven’t been able to properly commit the time to do the research required to make it all play nice.
I’ll be doing this sometime soon 👍