How to deploy your Node.js service
blog.gosquadron.com
blog.gosquadron.com
Automatic deployment is usually 3-10 steps that need to be run in a remote server. How's this better that a simple script that sshs into the server/servers, CDs into the project dir and does `make update`, which pulls some branch, runs any migrations and does an `apache gracefully` or similar whatever needed for the update?
This is after two tries to get my company over to a Vagrant based setup, once using puppet and a second using bash scripts. Unfortunately neither got us off the ground fast enough to make it viable.
Those + some bash scripts to sort out credentials and relationships between services - sorted!
PSA: One of the creators of Squadron.
really though, how is this any better than ansible?
When im ready to run something on testing, for example, I checkout testing, merge from development and push.
In the remote server, the code it the repo is running with pm2. I use a post-receive hook to npm update everything and pm2 restart.
If everything is ok, and I want to deploy into production, I do the same thing but merging production branch instead.
When I see tools like this, I tend to think that im missing something, or that there might be something wrong with what I do.
What do you think?
I try to use services or tools that do as much as possible out of the box. It means that I didn't have to manually configure much, which means it will be easier to understand after long periods of time. I know it isn't very hacker-like, but I personally feel there is a gray area that might create more problems than it solves, and I tend to stay on the "safe" side of things.
Thanks for taking the time though.