![]() ![]() The first thing I did was use the quick start for python. You get all the benefits from the container: you abstract runtime, libs, binaries, code and configuration from the underlying host. You get all the benefits of VSCode and its extensions, and the ability to use a container to code, test and debug. The remote-container extension makes working with containers much easier. We do not want to spend hours figuring out what and/or why something broke. We look for ways to keep our main system uncluttered and safe because we need it to be functional every day. Some develop inside the container but most don't. We craft development docker containers with the tooling we need and switch back and forth between the main system where we code and the container were we run. We use Virtualenv to avoid installing python modules system wide. ![]() We use specific Gemsets for different projects. We install RVM or NVM to play with different ruby or node versions. We quickly spawn a local virtual machine with Vagrant: we can break whatever we want in there. ![]() We don't want to risk breaking a well tuned system we rely on for our day to day work! So, what do we do? , crumm, a lot of runtimes and libraries in different versions on his/her main machine? Who installs the latest and greatest to test it out on his/her main system? Aaaah, thought so. This will allow beginners to follow along as well.īefore we start, just out of curiosity, who installs a ton of sh. We will concentrate on remote-container by using the first steps of a Python/Flask tutorial. Here we'll take a look at an extension that makes it a lot easier to develop inside a container. I have already talked about the remote-ssh VSCode extension that changed my way to code in Python for small electronics projects with a Raspberry Pi. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |