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
Does it have logs?
celery_beat
celery_worker
db. A lot of errors here, but I think I recall reading somewhere in the issues that it doesn't matter. I'd have to double check that.
redis
web
I don't think postgres having fatal errors like that is normal. I'd check the user it's running as and the permissions on the files/directories/volumes.
You have a permissions issue with pg_logical/snapshots": Permission denied. Check that your volumes exist in /var/lib/docker/container (or something close) and that the user running docker can create a test file in the local directory (likely a db directory in the docker root)
What's your docker-compose.yml look like? Especially any volume mounts
I have the folder. I chown and chmod it as it should be. Looks like it reverts back to the wrong permissions though. Don't know why.
Here is my docker-compose
Spot on. You can’t self host without reading app and system logs.