Feature docker vagrant ssh options #2923
Merged
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 adds options to start subsequent actions after executing Vagrant start and Docker deploy
Related Issue
None
Description of the solution adopted
Added/Edited scripts which not optionally allows for:
Vagrant (
dev-tools/vagrant
)ssh.sh
as shortcut forvagrant ssh {machineName}
destroy.sh
as shortcut forvagrant destroy -f {machineName}
./start.sh develop --ssh
which automatically invokesssh.sh develop
to jump into the newly started machineDocker (
deployment/docker
)docker-logs.sh
as shortcut fordocker compose -f {composeFile} logs -f
./docker-deploy.sh --logs
which automatically invokesdocker-logs.sh
to open container logs right after the deploy.Powershell script have been updated too
Screenshots
None
Any side note on the changes made
Just some cleanups and improvements.
Power shell script now forcibly require PowerShell at least version 7. See https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_requires?view=powershell-7#-version-nn