home.social

#renovatebot — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #renovatebot, aggregated by home.social.

fetched live
  1. I just launched a new project: renovate-operator

    A Kubernetes operator that deploys and manages Renovate Bot at scale! 🤖 Automate dependency updates across repos with scheduling, Git platform discovery and Helm/Kustomize support. Open source & community-driven.

    Would be happy to get some feedback, boost is also welcome :mastolove:

    github.com/thegeeklab/renovate #K8s #Kubernetes #GitOps #opensource #renovatebot

  2. Технический долг — это не только legacy: как мы уменьшаем разброс решений между Go-сервисами

    Когда компания растёт из одного продуктового направления в несколько, технический долг начинает выглядеть иначе. Проблема уже не в «старом коде», устаревших зависимостях или сложной поддержке legacy-системы. Долг начинает накапливаться в расхождении инженерных решений между сервисами. Для нас в QIC digital hub это особенно заметно на фоне миграции на новый Go-бэкенд. Исторически платформа развивалась на разнородном стеке: разные части системы были написаны на разных технологиях. Сейчас мы постепенно переезжаем на Go. Часть сервисов уже в проде, часть ещё на пути. Именно в такой момент легко создать новый слой техдолга поверх старого: переписать поведение на новом языке, но оставить команды один на один с десятками одинаковых инфраструктурных задач, которые каждая решает по-своему. Мы стараемся не просто переносить сервисы на новый стек, а одновременно пересобирать инженерную инфраструктуру вокруг них. В нашем случае это несколько взаимосвязанных инструментов: - go-kit — общая библиотека с переиспользуемыми инженерными решениями; - go-service-template — шаблон, который делает эти решения стандартным способом запуска нового сервиса; - shared-renovate-config — общий Renovate-конфиг с единой политикой обновления зависимостей для всех репозиториев. Ниже — честная инженерная история о том, как мы стараемся замедлить накопление нового техдолга в растущей мультидоменной платформе.

    habr.com/ru/articles/1056628/

    #golang #микросервисы #технический_долг #архитектура #рефакторинг #стандартизация #шаблонизация #управление_зависимостями #бэкенд #renovatebot

  3. @electret nice, I‘m currently also experimenting with controlled through with a self hosted . updates the helm chart of the each night and creates pull requests which gets validated by a worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.

  4. I would really like to move away from #GitHub with my projects towards #Codeberg.
    I still would like to use #RenovateBot by Mend, but they don't offer it with Codeberg. Any good way to keep it running also on Codeberg?

    Reposts appreciated.

    #di_day

  5. This has been what's it's all been for...

    Bots raising PRs when a container is updated. I have the ability to roll back these back if something goes wrong and the same is true of OS updates.

    #bootc #RenovateBot #Podman #Quadlets

  6. RE: mastodon.social/@connel/115382

    I fixed it! I had to mount the host's podman container storage directory in my #Gitea runner but I think I'm out of the woods.

    I did look at Nix but now I've got a working build pipeline, I'm hoping I'll be able to build something really cool with #RenovateBot

  7. 1/5 Heya Fed, Hint of the day for the devs out there: I was heavily reliant on Dependabot to keep my project's software dependencies versions up to date (you are keeping your dependencies up to date, right?).

    Some colleagues who are deeper into OSS told me to try Renovate, but I mostly dismissed it as just alt tech.

    docs.renovatebot.com/

    #devops #renovatebot #oss #dependabot #automation #softwaremaintenance #ci #monorepo #buildtools #developerexperience #selfhosted

  8. 1/5 Heya Fed, Hint of the day for the devs out there: I was heavily reliant on Dependabot to keep my project's software versions up to date (you are keeping your dependencies up to date, right?).

    Some colleagues who are deeper into OSS told me to try Renovate, but I mostly dismissed it as just alt tech.

    docs.renovatebot.com/

    #devops #renovatebot #oss #dependabot #automation #softwaremaintenance #ci #monorepo #buildtools #developerexperience #selfhosted

  9. I should've known an alternative existed for . 😅

    is pretty interesting. You can run fairly quickly. And it supports and . 😎

    github.com/renovatebot/renovate

  10. What I did in the last weeks (part 2):

    All of my k3s clusters (and I have a few of them for $REASONS) are now running either #fluxCD or #argoCD. So everything #gitops now.

    In general, I like the lightweightness of fluxCD, not having to run Redis and whatnot. But having a GUI is sometimes nice, even though the flux CLI is really easy to use and very intuitive.

    And of course, #renovatebot is watching all repositories and sending merge requests to update things in the clusters. Nice!

    #k3s #homelab #kubernetes #k8s #fluxCD #ArgoCD #GitOps

  11. I'm setting up #renovate for our internal #gitlab and I can see already how much I missed this tool and how useful it will be. Should have done this way earlier 😊

    #renovatebot

  12. Last night this beauty of a PR got finally merged github.com/renovatebot/renovat

    So when github.com/NixOS/nix/issues/80 gets worked around or resolved, #renovatebot will finally bump your flake.lock 🎉

    So happy to finally get this out of the door!

    #NixOS #flakes #nix

  13. Managed to migrate my first #Truecharts app from #TrueNAS to #Talos.

    Do this only if you need another hobby. It is definitely nothing like the comfort the TrueNAS App Catalogue and UI provided.

    But i like #Kubernetes and so it is fine for me, to play around with #CertManager, #RenovateBot, #FluxCD and #VolSync. Just have to compare resource consumption now 😅

  14. Workaround for my earlier problem:

    When you want #RenovateBot to update images that are cached on an #azure container registry, it will not work because Renovate can not see new versions that have not yet been pulled and cached.

    You can mitigate this by configuring a registryAlias for Renovate that points on the original registry (i.e. docker.io) where the cached images come from. Renovate will find new versions there and create Pull Requests for them.

    docs.renovatebot.com/configura

    #DevOps

  15. @jgarber maybe projects like #renovatebot could add automated warnings about 'dangerous' gems as well.

    I like that idea of yours.

    Maybe somebody could create an issue for that:

    github.com/renovatebot/renovat

  16. This week I have been building some #container images for e.g. #renovatebot and I must say I really dig #Chainguard and the #WolfiOS ecosystem. Building an image locally using #apko was a breeze. Building on #GitHub was easy due to their Github Action.

    And the long list of packages available is nice.

    And the list of CVEs in the image is really short.

    I'll try to get my hands dirty with melange and try to build a Pluto package for WolfiOS...