4 ms·
And what would you recommend? Also, if you fail to see the value in this, then I'd ask what you would use: - When you need to work on multiple products with d
by adriancr 4y ago
And what would you recommend?
Also, if you fail to see the value in this, then I'd ask what you would use:
- When you need to work on multiple products with different environments.
- When you want to temporarily spin up development environments on powerful machines for parts of your work and rest of the time develop locally?
- When you want to pass an identical environment to someone else and have it just work.
- fatih-erikli 4y ago- When you need to work on multiple products with different environments. You interact with APIs. You don't have to install a database or another daemon to your local computer. - When you want to temporarily spin up development environments on powerful machines for parts of your work and rest of the time develop locally? This has never happened. - When you want to pass an identical environment to someone else and have it just work. All the dev stacks has something like package.json
- adriancr 4y ago> You interact with APIs. You don't have to install a database or another daemon to your local computer. How about the people writing the APIs?, or the ones writing the servers?, or the os, or database, etc? > This has never happened In your case, use a bit of imagination. > All the dev stacks has something like package.json That is a very broad statement and in my experience, no.