Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support monorepo setup #16

Open
mickmister opened this issue Jul 20, 2024 · 0 comments
Open

Support monorepo setup #16

mickmister opened this issue Jul 20, 2024 · 0 comments

Comments

@mickmister
Copy link
Member

A given repo may have multiple apps defined in the same repo. The GitHub releases need to be coordinated between each app.

In a given release, there can be an rpi-deploy.json file that contains info like the app's id/name. Then rpi-deploy can figure out what application needs to be spun down and back up.

Different tag prefixes can be used to kick off different GH actions workflows in the source repo. Like this:

  • midibuddy-v0.2.0
  • jamtools-v0.4.2
  • jamtools-v0.5.0-rc1

The source repo will then create a new release with the artifacts related to that particular app. rpi-deploy can be configured to pull pre-releases or not. Fetching just the latest release will not be sufficient then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant