Update readme.rebase.fixes #111
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Observer table probably should have already been in a previous PR. The SATCAT update error is of unknown origin.
interplanetarychris
added
documentation
|
With the packaging updates to trusat-orbit this PR has been superseded by the work in branch dev.chris.package. I re-based that branch against the branch in this PR, so the eventual merge should be straight-forward. Will submit a PR when @Kmoneal is ready to review-one, and update the sever-side process to adjust to the new structure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@Kmoneal Here is an initial Docker development environment build. It creates a fully working local environment, populated with sample data from SolarLyra, in just 4 steps. It takes a few (~6) minutes to build on my machine.
The Docker build currently uses the
update-readme.rebase.fixesbranch, and the steps can be found at the end of that branches Readme.md fileI think there are some refinements we can make to config files, build files, and environment variables to further streamline this, and we can discuss that after you've tried it out.