Main

Basically, these tools are shared among all stacks, so they don't need to be containerized. Examples: Git, SSH, etc.

[x] Save .gitconfig to config repo?
- Can't configure email for privacy reasons: provide instructions
[x] Dockerize?
- Load SSH credentials via volume
  - Files don't have correct permissions
- Couldn't I just make sure to never push the docker container? Well, there are issues with docker context and ADD
  - Basically, I can't add the private files from outside the Docker context
  - Possible: I could just move the files into the directory as a part of setup, and include them in the .gitignore
- Honestly, it might be better to use Vagrant
  - Have to add project files via volume
[x] Add eval $(ssh-agent -s)
[x] Make sure to remove username hard coding from scripts
[x] SSH
- SSH config files (e.g. Git)
[x] Git
[x] Add SSH config to project
[x] Recommend adding SSH keys manually
[ ] Remove automatic cleanup of dev-tools containers. Name them instead. Update docs
[x] Slow volume file I/O means putting yarn in a docker container is kinda pointless
- But this is not the case on Linux, so nevermind
[ ] Combine dev-tools with vim. Just exec into it to have both Vim and various other development tools
- This would prevent publishing of pre-built images

`dev-tools` Specializations