3 ms·
Odd you put one click deploys in there though. It's quite trivial to get setup yourself, even if you are running your own servers/VMs and saves a ton of time (a
by mattmanser 7y ago
Odd you put one click deploys in there though. It's quite trivial to get setup yourself, even if you are running your own servers/VMs and saves a ton of time (although I prefer it to be a couple of clicks).
And once you have it for one project, you can usually adapt the script or process for others.
- deleted 7y ago[deleted]
- ben_jones 7y agoThe problem is you have to maintain it as your infrastructure goes. Pretty soon you should be setting up a staging and test environment, and then you have to deal with segmenting data between environments and it kind of spirals from there. As a general rule of thumb you need to be really cautious not just of the initial work to implement something, but the medium term operational overhead which 1-click deploys falls into. That said I still support 1-click deploys early on. It's just not so easy as adding a githook to trigger a script.