Release r23248 · wimpysworld/obs-studio-...
New build of OBS Studio Portable is ready: https://github.com/wimpysworld/obs-studio-portable/releases/tag/r23248
19 Replies
ok so how does this work, do we just rebuild the thing?
Yeah
We’re using this link: https://github.com/wimpysworld/obs-studio-portable/releases/latest
In the containerfile
So rebuilding will pull the latest release
ok so worst case 24h delay, I kicked it off: https://github.com/ublue-os/obs-studio-portable/actions/runs/6086785460
We could use the pull app to build everything in sync
we’d keep our own “fork” but it’s just synced
I think in general what we need (for not just obs), is a method to just check an upstream container regularly and build if changed.
There’s no upstream container in this case
I guess you mean after we push the Containerfile upstream
If its code on server its easy but i think i made a action that can do that as well once so i think i could write it
I think he means something with which to vheck if base repo has changed
Oh I see, it seems there be no good way of doing that from GitHub actions as it would need to remember across invocations
Push sha value to repo
We could check tags or releases though
Or use a secret
@j0rge i can prototype something later today with github action as compute platform so we do not need a server or some sort of lambda/azfunc
yeah like it'd be cool if we pushed a fix to the config repo, and then it just caused everything downstream to rebuild
GitHub
action - Kick off a build when the base image updates · Issue #25 ·...
We need a method in the github action to ensure we kick off a build when the Fedora base image changes so there's as little lag between builds. Additionally it'd be neat to implement these ...
feel free to assign yourself