Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
deploybot.com
Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
1–10 of 41 posts
Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#2Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#3Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#4Seems like a pretty neat service. To save others some time, they don't have a free tier, you can't host it yourself, and they use Docker for builds before deployments: http://support.deploybot.com/article/1028-plans-and-pricing
Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#5Seems like a pretty neat service. To save others some time, they don't have a free tier, you can't host it yourself, and they use Docker for builds before deployments: http://support.deploybot.com/article/1028-plans-and-pricing
Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#6Seems like a pretty neat service. To save others some time, they don't have a free tier, you can't host it yourself, and they use Docker for builds before deployments: http://support.deploybot.com/article/1028-plans-and-pricing
Suggestion to all companies: please have a /pricing/ page.
Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#7Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#8Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.
#9What many don't seem aware of is that plain pull requests, in combination with CI, entirely kill the need for a deploy app/bot.
This is how I do it at my current company:
* use plain git flow (master/develop, hotfixes, etc)
* use additional explicit branches per deployment target (e.g. master-spain for http://myapp.es, master-mexico for http://myapp.mx).
* Protect these branches using github/bitbucket 'protected branches'.
* open a PR from master to master-spain for performing a deploy of said target, detailng nicely what is being deployed and why.
* instruct CI to deploy my app on each build of master-spain. master and develop are never deployed.
This setup has the same benefits (and then some more) than competitors: * Explicit deployment authors, reasons, timestamps
* Impossible to deploy red code
* Impossible to deploy code not in master
* Impossible to deploy concurrently to the same target
Hope it helps someone!