one thing I'm not willing to self host is vault/bitwarden. My whole life is based in my password manager. I imagine Bitwarden inc has a lot better security than me, and if I lose access to it I'm stuffed.
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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
What are they going to get an encrypted blob.
Had this exact thing happen to me. I was hosting vaultwarden on a raspberry pi and then it fell over. My client devices had caged versions of my vault, but I couldn’t make changes to it. I quickly moved over to Bitwarden and it’s been fantastic.
yup, BW is awesome. and mostly free. I use BW too, but not self hosted.
Already updated yesterday 🤓 All hail the mighty renovate
Renovate?
I have all my compose stacks in git. They're deployed from their git repos with Komodo.
Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there's a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It's a great semi automatic way to handle updates without giving up control.
There's a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo
It's a bot to create PR's with dependency updates
Might be a stupid question, but how are PR's connected to your server deployment?
Copying my other comment. It opens PRs to change the tag from the docker image.
I have all my compose stacks in git. They’re deployed from their git repos with Komodo.
Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control.
There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo
Renovate? Hrmmmm
Hrmmm?