- Node 14
- Gatsby CLI
- MongoDB
./run.sh
or
docker-compose --project-name web -f ./docker-compose.yml up --build
Use the .env.example file and rename it to .env in order for docker-compose to pick it up.
In the .env file you can:
- Set
SSH_PUB_KEYto yourid_rsa.pubkey file. Currently it's defaulted to~/.ssh/id_rsa.pub. There is no password set for the docker user created, so the only way to login is through the SSH public key. - Set the
LOCAL_WORKSPACE_DIRto desired. This dir on your machine will be mapped to the/workspacedirectory on the container. Currently, it's set to the directory above the docker-general repo dir. - Set the user desired in docker to be created. Currently it's set to
admin. This will be the only user able to login to the docker through ssh. NODE_VARIANTcan be set to the desired Node version install. Currently set to14.xGIT_USER_EMAILEmail for git commitsGIT_USER_NAMEFull name for git commits
- Startup the container through the above commands.
- Download VSCode Remote SSH.
- Click on the "Remote Explorer Extension" in the Activity Bar
-
Click on the
+icon to add a new SSH host. -
Type
ssh -o "StrictHostKeyChecking=no" -o "UserKnownHostsFile=/dev/null" admin@localhost -p 2222and pressEnter- The reason for the arguments is because everytime the container is created a new key is created for the container. So we can tell SSH to not worry about adding the container into the known_hosts.
-
Select the SSH config you want to update.
- Now
localhostshould be in the list of SSH Targets. From here you can hover over the hostname and to the right there is a "Connect to host in new window" icon. - Click on "Open folder..." and navigate to the folder you want in the
/workspacedirectory and select the project folder you are working on. - This folder in the future will show up in the Remote Explorer and you can just navigate directly to the project folders you have setup under the SSH Target.
The image was setup with Node on Ubuntu because VSCode Remote Extension currently does not support Alpine Linux arm64, so M1 Macs are not currently supported.