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

Consider setting up trusat-backend with GIT sub-modules #115

Open
interplanetarychris opened this issue Apr 10, 2020 · 0 comments
Open

Consider setting up trusat-backend with GIT sub-modules #115

interplanetarychris opened this issue Apr 10, 2020 · 0 comments
Labels
enhancement New feature or request
Projects

Comments

@interplanetarychris
Copy link
Contributor

To provide better configuration control across trusat-backend, trusat-frontend and trusat-orbit, we should consider using GIT's native sub-module feature .

A quick look would seem to imply that a reasonable configuration would be to have trusat-backend be the "primary" repository, with -frontend and -orbit as sub-modules (tagged to a specific version/release/branch).

@interplanetarychris interplanetarychris added the enhancement New feature or request label Apr 10, 2020
@interplanetarychris interplanetarychris added this to To do in TruSat via automation Apr 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
TruSat
  
To do
Development

No branches or pull requests

1 participant