Skip to content
This repository was archived by the owner on Dec 28, 2023. It is now read-only.
This repository was archived by the owner on Dec 28, 2023. It is now read-only.

docker-compose up works, but remote debugging doesn't #5

@DragonSpit

Description

@DragonSpit

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions