Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow different concurrent development environments on a single machine

See original GitHub issue

Environment

Python version: 3.8.5
Nautobot version: 57c8b8f1e8cc (v1.0.4b1)

Proposed Functionality

The project_name specified within “invoke” should be taken into account when building the docker image with invoke build

Use Case

As a developer I want to be able to have different development environments on the developers machine (different projects).

The problem with the current invoke build version ist, that the container image name will not be affected by the docker-compose --project-name ... parameter because it is fully specified as image name in docker-compose.yml file. Thus overwriting the image of all the other project when invoke build is executed.

services:
  nautobot:
    build:
      args:
        PYTHON_VER: "${PYTHON_VER}"
      context: ../
      dockerfile: docker/Dockerfile
      target: dev
    image: "networktocode/nautobot-dev-py${PYTHON_VER}:local"
    ports:
      - "8000:8080"
    depends_on:
      - postgres

Database Changes

None

External Dependencies

None

Issue Analytics

State:
Created 2 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

glennmatthewscommented, Jun 24, 2021

Good suggestion! I think fixing this may be a bit more involved than just adding the project_name; we also need to consider making it possible to override the exposed ports (8080 and 4444) by each running development environment.

0reactions

glennmatthewscommented, Aug 5, 2021

I’ll close this then - thanks! FYI there are some workflow changes here in 1.1.x - if you get a chance to review #782, it would be appreciated!