Closed ciaransweet closed 3 years ago
Makes me realize at some point we might need to package this so it's a utility that can be installed and/or run on a per repo/project basis.
I'm still a little confused with this change, if someone deploys, ssh, starts some code, disconnects, and then wants to come back later to check on the instance, how they remember which instance to ssh to?
Makes me realize at some point we might need to package this so it's a utility that can be installed and/or run on a per repo/project basis.
I'm still a little confused with this change, if someone deploys, ssh, starts some code, disconnects, and then wants to come back later to check on the instance, how they remember which instance to ssh to?
@wildintellect not sure what you're implying with this? What would be packaged as a utility?
Also @wildintellect if something doesn't make sense, you're welcome to reject the PR haha!
What I am changing
TL;DR:
This PR adds some Quality of Life improvements to the repository, namely pinning versions and making overall interaction with the project a bit easier
Closes #13 #12
How I did it
Dependencies
Pipfile
andpackage-lock.json
Makefile
commands to abstract installation of 'prod' vs 'dev' dependenciesCDK
cdk/
so that we're explicitly keeping it in one location and not the root and another directoryGeneral
.gitignore
Makefile
to match the more recent style I've used inpangeo-forge-aws-bakery
make ssh-to-instance
to abstract out ssh'ing logicREADME.md
:pangeo-forge-aws-bakery
s styleMakefile
section.env
table.env
file out toexample.env
Github
How you can test it
No real functional changes as such, a CI build should happen which should pass on
linting
.Otherwise you can re-run through the instructions and see that the deployment still functions.
Note:
I do intend on adding some unit tests for the
utils
code eventually.