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
When I installed radicale last, i had problems with auth and exposing it. I think either I misunderstood something or it was left as an exercise for the reader. Anyways...
I'm a noob and I managed to set it up following mostly these instructions that make user of this docker compose file. I remember I had to do something slightly different, but I managed to figure it out relatively easily. You could have a look at it and see if it helps.
The documentation says what settings you need to enable for it to work. It also says that it takes the remote user in the X-Remote-User header. I use Authelia and it puts the remote user in the Remote-User instead, so i added a middleware to traefik that renames the header to the one expected by radicale. The only problem remaining is that radicale presents the auth page anyway, and you have to login with the same username as the auth header but with any password