add native GitHub release flow for orion & orion-scheduler#2105
Conversation
Add a tag-driven GitHub Release workflow that builds and publishes the Orion Linux amd64 runner bundle with checksums. Document the release bundle layout, remove obsolete Orion Docker runtime files, and preserve executable permissions for runner scripts.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 957a631323
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| WorkingDirectory=/opt/orion-scheduler | ||
| Environment=RUST_LOG=info | ||
| Environment=CONFIG_PATH=/etc/orion-scheduler/target_config.json | ||
| # Override these in /etc/systemd/system/orion-scheduler.service.d/*.conf if needed. |
There was a problem hiding this comment.
When an operator uses the documented PREFIX override in install.sh, the binary is installed under $PREFIX/bin, but the unit installed verbatim still starts /opt/orion-scheduler/bin/orion-scheduler. In that non-default install path the service will enable successfully but fail to start; the same raw-unit issue also affects the documented ETC_DIR/SERVICE_USER overrides. Template the unit at install time or remove those overrides from the installer contract.
Useful? React with 👍 / 👎.
2a0b5fa
2 participants
No description provided.