38
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Aug 2025
38 points (100.0% liked)
Selfhosted
50966 readers
496 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Sure. I wrote the docker-compose file in the repository. Unless something major has changed, it should be pretty straightforward to just clone the repo and then run
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
docker-compose.yml contents:
Don't commit secrets to git!
Damn mobile formatting.