Repository navigation
Installer: status, stop, start and uninstall commands (#372) - #381
Merged
Merged
Conversation
This file contains hidden or 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
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.
Closes #372.
What
install.sh status | stop | start | uninstall [--remove-data] [--yes] [--instance <name>]works from a checkout, or from the web against the installed checkout. From the web, nothing is fetched or moved. Everything is found by the Compose project labels.statusreports: instance, project, installer version, catalog, containers, port,/health, NetBird and the CKAN set up for the Endpoint. It is read-only and writes no log.stop/startusedocker stop/docker starton the project's containers, plus the CKAN set up for the Endpoint. Containers start as they were created, so the port stays (related to Restarting an Endpoint with docker compose loses its port #370).uninstall:--yeswhen nobody can answer;.env.backup.*files;.envand the install state, so a re-install brings the Endpoint back with its data;--remove-data, also removes the volumes,.envand the state;EP_API_PORT,CKAN_DIRandCKAN_CREATED.Tests
install/tests/test_lifecycle_commands.py: 22 tests, failing onmain.statusreported it;stopleft the port not answering;startbrought it back healthy on the same port, with its bucket intact;uninstallkept the volumes, and a re-install came back with the data;uninstall --remove-dataleft nothing behind;statusreported two Endpoints installed with 0.34.56 correctly.Release 0.34.63.