3 ms·
At Nitrous, we use Nitrous Pro to develop Nitrous Pro, and Nitrous Pro requires a pretty complex setup (minimum 10+ components required to run). We did it by c
by raingrove 11y ago
At Nitrous, we use Nitrous Pro to develop Nitrous Pro, and Nitrous Pro requires a pretty complex setup (minimum 10+ components required to run).
We did it by creating a master Docker image that runs Docker in Docker, with sub-containers running individual components. Nitrous Pro allows you to create development environments in the cloud with Docker images, and with the master image we created, we are able to recreate a dev env and onboard a new employee in only 10+ minutes in Nitrous Pro.
I won't say that creating this master image was a trivial task, but we provide many ready-to-go templates that are sufficient for most people to get started, and we are actively looking for ways to make customization of templates easier.
- skuunk1 11y agoHi, I have been a long time Nitrous user (I use it with my Chromebook). Do you have any plans for migrating current users to Nitrous Pro? Thanks
- ajhit406 11y agoThere's a free plan on Nitrous Pro, so you can signup to reserve your free workspace (we're rolling out free workspaces, if you pay it's available immediately). We wrote about a few ways you can migrate your data to Nitrous pro here: http://docs.nitrous.io/v1.0/docs/migrate-your-data-to-the-new-platform http://docs.nitrous.io/v1.0/docs/migrate-your-data-to-the-ne...
- skuunk1 11y agoThanks very much!
- techdragon 11y agoAt this point I would have just eliminated the IDE from my toolchain and used continuous integration and continuous delivery. That setup sounds obscenely complicated.