this post was submitted on 12 Feb 2026
104 points (99.1% liked)

Selfhosted

56379 readers
1123 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
104
Vaultwarden security update Feb 10 2026 (github.com)
submitted 2 days ago by megaman@discuss.tchncs.de to c/selfhosted@lemmy.world
12 comments fedilink hide all child comments
 

GHSA-h265-g7rm-h337 (Publication in process, waiting for CVE assignment) This vulnerability would allow an authenticated attacker that is part of an organization to access items from collections to which the attacker does not belong

you are viewing a single comment's thread
view the rest of the comments
[–] tofu@lemmy.nocturnal.garden 20 points 2 days ago (2 children)

Already updated yesterday 🤓 All hail the mighty renovate

[–] Natanox@discuss.tchncs.de 2 points 1 day ago (2 children)

Renovate?

[–] tofu@lemmy.nocturnal.garden 7 points 1 day ago

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

[–] qaz@lemmy.world 1 points 1 day ago (1 children)

It's a bot to create PR's with dependency updates

[–] Natanox@discuss.tchncs.de 2 points 1 day ago (1 children)

Might be a stupid question, but how are PR's connected to your server deployment?

[–] tofu@lemmy.nocturnal.garden 2 points 1 day ago

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