tofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 11 hours agoForgejo v17.0forgejo.orgexternal-linkmessage-square12linkfedilinkarrow-up1120arrow-down10
arrow-up1120arrow-down1external-linkForgejo v17.0forgejo.orgtofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 11 hours agomessage-square12linkfedilink
minus-squarecorsicanguppy@lemmy.calinkfedilinkEnglisharrow-up3·10 hours agoYou updated f’jo with renovate? Badass.
minus-squaretofu@lemmy.nocturnal.gardenOPlinkfedilinkEnglisharrow-up5arrow-down1·10 hours agoYeah, I keep forgejo’s compose file in forgejo. Changing the file triggers my Komodo which pulls the new file and applies it. It may interrupt a pipeline triggered by the merge or similar, but it’s generally fine.
minus-squarecorsicanguppy@lemmy.calinkfedilinkEnglisharrow-up1·7 hours agoI’m non-container - too much time in security - but that’s a wicked workflow. Well done.
minus-squareVictor@lemmy.worldlinkfedilinkEnglisharrow-up2·5 hours ago too much time in security By this, do you mean there’s a lot of work with security when running in a container?
You updated f’jo with renovate? Badass.
Yeah, I keep forgejo’s compose file in forgejo. Changing the file triggers my Komodo which pulls the new file and applies it. It may interrupt a pipeline triggered by the merge or similar, but it’s generally fine.
I’m non-container - too much time in security - but that’s a wicked workflow. Well done.
By this, do you mean there’s a lot of work with security when running in a container?