chore(build): automate jumphost setup #412
Merged
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
alexanderleegs
approved these changes
Mar 31, 2022
harishv7
pushed a commit
that referenced
this pull request
Feb 17, 2023
* chore(readme): add .md file ext for correct rendering * chore(package.json): add new commands for db stuff * chore(package.json): add commadn for local migration * docs(readme): update for new commands
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.
Problem
Jumphost set up is tedious and prone to errors. Developer friction could be eased by automating parts of the jumphost setup and making it a fixed command.
Solution
.sshfolder for storing related information and shift env files + credentials thereNotes
jumpcommand has actually been tested; thedb:migrate:<env>command has not as the corresponding migrations have already been ran