view the rest of the comments
Selfhosted
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!
Sorry i don't have experience checking docker logs... How do I go about that?
In the same place as you run your
docker compose up
command you just typedocker compose logs
Huh....so the log is just an almost infinite loop of these:
Just for clarity's sake, here's my docker-compose.yml:
I literally haven't changed anything from default as it was a test, even the password fields.
Your passwords for the database does not match.
But the error is about it not being able to reach the database on the hostname.
I can run it with this compose file:
Hmmm thanks but I'm not using traefik...Is it part of the needed setup?
No. You can leave that out. That was just me showing you that it runs on my machine, with that setup. Just bind the port instead.
Just came to say thanks...Yeah eventually after copy-pasting it from scratch again, I got it running. Seems to be working now. Thanks again!