I don't like to have difference between my development setup and the production setup (containerized). I don't find it harmful to have a virtual env inside the container.
Do you ship your container dev to stage, stage to prod. OR, clone the repo at production server and run docker command, like, docker-compose up
docker-compose up
And thanks for your thought.
We actually use K8s for dev, staging and production clusters. For development, we have containers that're orchestrated by docker-compose.
docker-compose
The flow is: Test things locally, once done, deploy to dev, then move to staging and finally deploy on production.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't like to have difference between my development setup and the production setup (containerized). I don't find it harmful to have a virtual env inside the container.
Do you ship your container dev to stage, stage to prod. OR, clone the repo at production server and run docker command, like,
docker-compose up
And thanks for your thought.
We actually use K8s for dev, staging and production clusters. For development, we have containers that're orchestrated by
docker-compose
.The flow is: Test things locally, once done, deploy to dev, then move to staging and finally deploy on production.