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
Maybe Tandoor for recipes and Groceries from David Shay for shopping lists of all kind. So far the best multi User shopping list / app I ever had.
groceries got me interested, but I'm not able to get it working in docker. I am trying to run it behind caddy reverse proxy. All the containers are running, and it seems the couchdb database has been created but I get nothing when going to the url of the server and client. Just blank page.
Hmm, what do docker logs -f tell? I made myself a compose file and use traefik. Not on my PC atm, but when I had problems getting it running, I made mistakes with the secrets. But that should show in the logs.
I get a lot of stuff.. The first time i tried to make a docker-compose myself based on docs, and it made the groceries db. But I found out you need a lot of settings for couchdb, so I tried to run the default files, and I got an error on docker-compose.yml file. It wouldn't run due to "restart: always" in the healthcheck of couchdb.
Now it seems it is complaining about JWT settings, even though I have base64-code in jwt.ini corresponding to the phrase in docker-compose.
groceries-server_1 | [07:30:22] ERROR: Cannot access database with encoded JWT key. Please check HMAC entry in jwt.ini. The hmac:_default value should be: c3F1ZWVnZWUtZmxhdG5lc3Mtb2NjdWx0aXN0LWNvbmZ1c2luZw==Which corresponds to the jwt.ini
[jwt_keys]hmac:_default = c3F1ZWVnZWUtZmxhdG5lc3Mtb2NjdWx0aXN0LWNvbmZ1c2luZw==I got a bad feeling about the whole thing.. I think I will stick to caldav + tasks.org for my shopping list, it has a much simpler setup..
Setup of the HMAC Key for the CouchDB was indeed the step I struggled with too. I think the first time I either made a mistake or used a broken Website to generate a Base64 value. The 2nd time my mistake was that I put in the Base64 value for the HMAC Key into the jwt.ini AND in the docker-compose.yml. But in the docker-compose.yml COUCHDB_HMAC_KEY, I had to put it unencoded and in the jwt.ini hmac:_default it has to be Base64 encoded. Maybe this is the thing you did wrong too?
I bet you are close!
On the other hand, if you are the only person using the shopping list and your current setup offers you what you need, maybe it is not worth it for you. For me it was (and updating when it runs is super easy, I promise!). The instant sync over all devices is great + it keeps working when I lose reception in a shop and syncs again instantly when I have internet again. But what makes Groceries for me are:
Oh, and adding a photo to an item is super useful if you are like me and need very close instructions what to get for your partner if you stand in front of a shelf with 100 different types of cheese which look all exactly the same to you... having a photo is sometimes a life saver for me :-)