When cloning into a new directory, docker-compose up works, after changing the name of .env file to .env-sample, since that's what docker-compose.yml is looking for. However, neither VisualStudio Code nor VisualStudio Code Insiders works to launch and connect to the docker-compose remotely.
Figured out an additional step necessary for this example to work in VS Code.
In requirements.txt file comment out psycopg2==2.7.4 --no-binary psycopg2 line and add psycopg2-binary==2.8.3. Then follow instructions in the Readme to start the node server in one terminal/shell, followed by Python/Django in another terminal/shell.
Also, thank you for posting this project. It made the ramp up on VS Code remote debugging much faster.
When cloning into a new directory,
docker-compose upworks, after changing the name of .env file to .env-sample, since that's what docker-compose.yml is looking for. However, neither VisualStudio Code nor VisualStudio Code Insiders works to launch and connect to the docker-compose remotely.Figured out an additional step necessary for this example to work in VS Code.
In
requirements.txtfile comment outpsycopg2==2.7.4 --no-binary psycopg2line and addpsycopg2-binary==2.8.3. Then follow instructions in the Readme to start the node server in one terminal/shell, followed by Python/Django in another terminal/shell.Also, thank you for posting this project. It made the ramp up on VS Code remote debugging much faster.