(2) We need to keep some history (to allow rolling back apps). So either need that in DockerHub or would need to move old images to ECR if we planned to fully nuke our DockerHub account.
Thanks for the article! I recently spent some time going through the process of learning VirtualEnv / Pip; after looking at several tutorials, agreed that this is one of the better ones out there. A few other things I saw in other articles that you might like to clarify (though I understand there's a tradeoff with simplicity/clarity).
(1) specifically state that `pip freeze` is how to create requirements file (as folks have said in comments already)
(2) add "further reading" link on VirtualEnvWrapper, as it adds some convenience methods to ease use of VirtualEnv
(3) the "yolk" package shows you what's currently installed; it can be helpful to `pip install yolk` then run `yolk -l` to view the different packages installed in each of your envs.
(4) when installing a package, you can specify the version, e.g. `pip install mod==1.1`, whereas `pip install mod` will simply install the latest
Perhaps only part of the resume. As a programmer, seeing real code, quality of commits, and working example projects made a big impression on me when recruiting intern-level developers. Also can see engagement with OSS, if applicable. Would be curious what sort of companies (size, location, focus, developer-to-other ratio) you're applying to and who they're seeking. Thanks!
The main downsides I see are:
(1) It would affect people's Docker workflow
docker pull org/foo:tag
->
aws ecr get-login
<run docker login command>
docker pull some-aws-url/foo:tag
(2) We need to keep some history (to allow rolling back apps). So either need that in DockerHub or would need to move old images to ECR if we planned to fully nuke our DockerHub account.