3 ms·

Do you mind if I ask whether you're using some kind of stack where auto-completion, intellisense, etc. is not dependent on any system libraries or dependencies?

Do you mind if I ask whether you're using some kind of stack where auto-completion, intellisense, etc. is not dependent on any system libraries or dependencies? Or do you just require the developer to install all of those libraries and dependencies on bare metal as well? If it's the latter, isn't that defeating half the purpose of containerizing it? My prediction is that you might be using a stack where it's not a big deal to isolate project-specific dependencies, npm or virtual-env style. And so in that context, it's not a big deal to ask developers to do a pip install -r requirements.txt or whatever, and then the docker container's job is just to emulate the runtime environment. It has just always made sense to me that the win of dockerizing your dev environment would be that you could reproduce it on another machine with a docker pull, so those sort of "half-way" workflows were unsatisfying to me. I'm always curious to hear how other people are doing it though - thanks for responding.

jzoch 7y ago
I think the idea others are getting at is using docker as a means of setting up a testing environment in your dev env, not using it as a dev env. I tend to do this (though the way you describe would be great too!). I develop locally with intellij but run my integration tests in a docker container (or a few) by packaging up my app in a container. I just make that container look like whats running in prod. Thats the magic. dev looks like prod.
dmead 7y ago
I'm not using intellisense or anything. the editor is left to the developer whos workstation the environment is running on. The docker approach for this is just to manage the build in a way that is like the CI pipeline. we have a shell script that adds some syntactic sugar around running docker in a consistent way, but other than that it's left to the dev how they want to manage the editor process.

jzoch 7y ago

I think the idea others are getting at is using docker as a means of setting up a testing environment in your dev env, not using it as a dev env. I tend to do this (though the way you describe would be great too!). I develop locally with intellij but run my integration tests in a docker container (or a few) by packaging up my app in a container. I just make that container look like whats running in prod. Thats the magic. dev looks like prod.

dmead 7y ago

I'm not using intellisense or anything. the editor is left to the developer whos workstation the environment is running on. The docker approach for this is just to manage the build in a way that is like the CI pipeline. we have a shell script that adds some syntactic sugar around running docker in a consistent way, but other than that it's left to the dev how they want to manage the editor process.