3 ms·
That`s how we do it in my company: - Clone project - Build container - Develop If you're in a polyglot shop there are HUGE productivity gains in not needing
by carlosf 6y ago
That`s how we do it in my company:
- Clone project
- Build container
- Develop
If you're in a polyglot shop there are HUGE productivity gains in not needing to setup your environment manually, or worse, risk that vital information about it is distributed as tribal knowledge.
Plus, if your project has external dependencies like DBs, S3, etc... you can use docker-compose with VS Code as well.
- majodev 6y agoCan only second this, we use a VSCode devContainer-based setup in all of our projects and even migrate our legacy projects to it (software agency). Here's our current base go template, you only need Docker+VSCode on your system to get started: https://github.com/allaboutapps/go-starter https://github.com/allaboutapps/go-starter Bonus points: * As all IDE operations solely run within the local Docker container, all developers can expect that their IDE will work the same without manual configuration steps. * We can easily support local development in all three major OSes (MacOS, Windows, Linux) and even support developing directly in your Browser through GitHub Codespaces. * Developing directly inside a Docker container guarantees that you use the very same toolset, which our CI will use to build these images. There are no more excuses why your code builds differently locally versus in our CI. Edit: format/typos
- harisund 6y agoDoes that force everyone to use VS Code only? Can non VS Code developers also work efficiently?
- panzerboy 6y agoYou could always run something like Vim/Neovim directly in the container. I, personally, hope that JetBrains comes up with something similar which will allow devs to use the same workflow with the JetBrains IDEs.
- majodev 6y agoyep, currently it forces our engineers to use VS Code or a terminal-based setup (or GitHub Codespaces). Hopefully Goland / IntelliJ catches up in this year...