Live data from Hacker News

Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.

deploybot.com

1–10 of 41 posts

Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.

#4
post #3

Seems 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

Does one need to have Docker configured to use this? I haven't gotten around to learning Docker yet.

Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.

#5
post #3

Seems 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.

#6
post #5
post #3

Seems 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.

Fair enough. They do list their prices but on their signup page https://signup.deploybot.com/signup/new

Re: Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.

#9
There's a number of startups doing some variation of this.

What 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!
Post reply on HN