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!
view the rest of the comments
There's a link in their Read Me on GitHub under the title about launching with Docker. Are you familiar with Docker?
Thanks...Yeah I saw it. I have a few docker things deployed. But the "getting started" section completely ignores setting up the Postgresql DB, which very clearly it seems to want. This is not listed as a requirement, but still hinted casually around whenever it mentions the user/pass, environment variables etc.
So...is there anywhere mentioned how to get the whole thing up and running, including docker and postgresql?
They have a
docker-compose.yml
file in the repo. It looks like it has everything all ready for you.Yeah...I copied the whole of it onto my docker-compose.yml. But after running a docker compose up, and after getting:
I still can't get to connect on http://myIP:3000, I get nothing, just a "unable to connect" firefox error. Is there anything I should set up/modify on the docker-compose.yml?
There will probably be something in the logs that tells you what is going wrong. Maybe it can't connect to the db, or maybe it's starting on a wrong port or something.
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!