feat: add service-setup subcommand #186
Open
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
magik6k
reviewed
Oct 9, 2024
LexLuthr
force-pushed
the
setup-service
branch
from
a4dd65f to
6f84758
Compare
LexLuthr
force-pushed
the
setup-service
branch
from
4fe510c to
bf55db1
Compare
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.
This PR modifies the following:
The guided-setup no longer create a curio.env file. It simply adds the DB related variables to .bashrc/.zshrc files. This allows users to run curio commands easily after guided-setup. In the end, it also prompts user to run
service-setupcommand.The new service-setup command creates the service files and then takes user input for DB and other vars to creates the /etc/curio.env file.