Show HN: Deploydo – Deployment made easy

The idea of these hosted deployment systems always scares me. Essentially you have no choice but to open SSH to the universe. This is far beyond best practices for at least a couple reason. The first would be that if at all possible you should be hiding SSH behind a VPN so that casual or not so casual attempts at breaking in to the server are made that much more difficult (this makes even people somehow getting a stolen private key a non-issue). The second would be that giving an &#x27;unknown&#x27; third-party this kind of access to your systems leaves you open to them being exploited and then exploiting you (and this scenario seems much more likely than someone guessing your password if you are using one on SSH for some reason).<p>All in all, deployment seems like something to me which I&#x27;d always want to keep in-house.

&gt; Ever asked yourself why deploying your projects to your servers is such a pain?<p>Personally, no. I haven&#x27;t heard it from my peers either. I just use rsync and quick scripts; others use PaaS (self-hosted or managed) that generally handles deployment pretty neatly.<p>The only place I&#x27;ve heard complaints about deployment is inside of large multi-tier organizations, where the problem boiled down to communication issues between dev and ops, not tooling.<p>I suspect I&#x27;m supposed to be the target audience here, but I&#x27;m not sure what problem this solves for me. On a first impression this looks mostly like a way to lock myself into a workflow that leaves a lot of unanswered questions (re: server security, platforms&#x2F;frameworks supported, etc), with very marginal benefits.

Web UI vs SSH is hardly the problem. More often, it&#x27;s setting the environment set up on the remote server that&#x27;s a terrible pain, then you have to set up domains and ssl and all that nonsense.<p>TL;DR configuration is pain to do manually every time, I hope you can make it go away. If you have ideas, comment below.

from the features page:<p>&gt; You can deploy nearly any programming language with our tool that works by just transferring the files<p>Maybe I misunderstand something, but this sounds like it trivializes the complexities of a typical deployment process. Services need to be restarted, code updated, database migrations run and so on...<p>I think for it to be successful you need to figure out a way to make automating those fragile deployment steps easy (and solid). This is a problem lots of configuration management tools are trying to solve (chef, puppet, ansible, fabric, capistrano etc). Or at least help integrate deploy.do with such tools.

&quot;Ever asked yourself why deploying your projects to your servers is such a pain?&quot;<p>I know exactly why it&#x27;s such a pain. Because every deployment tool available only deals with the <i>easy</i> parts.

Yes, I want to use a web interface like this, and the config management feature is something that I would find very useful.<p>No, I&#x27;m not comfortable giving a third-party service SSH access to our servers. Besides, all of our machines are on a private network behind a VPN. This is a best practice that most, if not all, companies should follow.

It is really worth having a .do domain? given that they are fairly expensive and seems like google will treat them as specific from Dominican Republic and not generic[1]?<p>[1]<a href="https://support.google.com/webmasters/answer/1347922?hl=en" rel="nofollow">https:&#x2F;&#x2F;support.google.com&#x2F;webmasters&#x2F;answer&#x2F;1347922?hl=en</a>

&quot;shinny&quot; should be &quot;shiny&quot; on this line:<p>We will do the rest for you. Just look on our shinny loading indicators while we are deploying your code without any downtime!

There&#x27;s a lot of explanations of source code deployments, but it never mentions compiled binaries. Is it capable deploying build outputs?

This is difficult for some setups, as it relies on an open SSH port. Our AWS instances are not publicly accessible, so this makes it hard.

Why not just use ansible?

&gt;You just provide us login credentials to [your] server ...