tofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 8 days agoForgejo v17.0forgejo.orgexternal-linkmessage-square16fedilinkarrow-up1169arrow-down10cross-posted to: selfhosting@slrpnk.net
arrow-up1169arrow-down1external-linkForgejo v17.0forgejo.orgtofu@lemmy.nocturnal.garden to Selfhosted@lemmy.worldEnglish · 8 days agomessage-square16fedilinkcross-posted to: selfhosting@slrpnk.net
minus-squaretofu@lemmy.nocturnal.gardenOPlinkfedilinkEnglisharrow-up7·8 days 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·8 days agoI’m non-container - too much time in security - but that’s a wicked workflow. Well done.
minus-squareVictor@lemmy.worldlinkfedilinkEnglisharrow-up4·8 days ago too much time in security By this, do you mean there’s a lot of work with security when running in a container?
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?