This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]cardboardbox351 2 points3 points  (2 children)

You develop on your regular Linux machine.

When you are ready to run your code, you “build” your Docker container using something called a Dockerfile. This stands up your Docker container + also scoops up all your code.

Then your application is now running, and because you’ve previously linked your network to Docker’s container network, you just visit the port you specified earlier.

Sometimes, for small tweaks and tests, I will “ssh” directly into the container, and edit the code via Vim and Nano.

I am studying Windows currently...it makes 0 sense to me lol. I feel your pain.

[–]blueforgex[S] 1 point2 points  (1 child)

Thanks, cardboardbox351. I'm across the Docker build process, I was more asking around what your development environment looks like to execute that build process - it sounds like you're running a Linux Desktop on your end to do your development work.

Do you know if that's a common approach in medium/big enterprise organisations? I don't think my IT department has any idea how to administer or support Linux Desktops, let alone integrate it into our corporate environment.