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
Thanks for your answer. I'm not sure what to look for in the browser's logs but here it is.
I have logs for all containers here:
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 have one container exited,
mediacms_migrations
, but I noticed it stopped right after the stack's setup and thought it would be used only for startup. Here are the logs for itIt looks like db is fried, I'd assume all the permission errors prevent it from running normally. Is there a healthcheck configured?