3 ms·
My favorite deploy is using a simple `git pull` instead of scp. I also avoid complex build tools when I can. You either need your built files in the repo or you
by codazoda 5y ago
My favorite deploy is using a simple `git pull` instead of scp. I also avoid complex build tools when I can. You either need your built files in the repo or you need to avoid them. Either are fine for my small personal projects. The only real exception I make is keeping any necessary secrets out of my repo. Those get dropped on the server manually.
This also solves the roll-back problem mentioned elsewhere. Just checkout the previous version (as long as you don't make any side effects like DB updates that are incompatible).
I admit, this requires relatively simple software.
- sbayeta 5y agoI do the same thing (just a couple os customers, o en Linode per customer). Hopefully I'll need something more complex eventually.
- OJFord 5y agoWhy pull, as opposed to push(ing to the server as remote)? Then you could have any necessary restart or migration or whatever run in a post-receive hook. I realise that's starting to get back in to tooling and config etc., but it's not that complex, and if you're already using git anyway...