It should be simple to re-run the script and have it bring the system to a known state. #27
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.
Aim:
Decisions:
If a git clone exists, it will be rm-d and cloned again. I thought about doing a git pull, but if people have made bad local changes it’s best to wipe it and pull from a known good source. I thought about checking for local changes, but the build process leaves local files, so the git clone is always “dirty”. I thought about making it halt, but I want people to just be able to run the script and have it work.
If people have already successfully installed in the past, installing base is going to reset it back to beocreate-4ch-blank, which I think is OK as again it’s a known starting point for someone who’s having problems. We also move (but not erase) beoconfig.json to allow people to set-up a system using the guided-setup.
More words than diff here, I expected this to be harder to do!