tofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 1 day agoForgejo v17.0forgejo.orgexternal-linkmessage-square16linkfedilinkarrow-up1154arrow-down10
arrow-up1154arrow-down1external-linkForgejo v17.0forgejo.orgtofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 1 day agomessage-square16linkfedilink
minus-squarecorsicanguppy@lemmy.calinkfedilinkEnglisharrow-up3·1 day agoYou updated f’jo with renovate? Badass.
minus-squaretofu@lemmy.nocturnal.gardenOPlinkfedilinkEnglisharrow-up6arrow-down1·1 day 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-up2·1 day agoI’m non-container - too much time in security - but that’s a wicked workflow. Well done.
minus-squareVictor@lemmy.worldlinkfedilinkEnglisharrow-up4·23 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?