"Deploy your apps from GitHub, Bitbucket or your own repositories to one or many servers in one click."
For example, I've got a python script that uses SSH to log into my servers and manually git pull from a master repository. I imagine that this service would replace that script.
The website says "70000" companies trust your product, with a list of the companies! Is that true? 70k company users already? Or is this something else being counted here?
Developer here. This tool is uploading files to your FTP/SFTP servers or Heroku/S3/Rackspace Cloud, whatever language they are written in. dploy.io doesn't run your applications, sorry for the confusion.
Your most likely going to have to restart some webserver at the very least modify symlinks to ensure a synchronized upgrade. Maybe you do support this but you have to actually explain what your service does.
Also the thing with the pricing is bullshit just put that on the front page don't make people wade through a signup form to get information about your service.
Also don't put a stupid tick next to the password box and then reject it for being too short.
Agree. We'll make some updates to explain it better. Our hope was that the more simplistic overview would be enough. For now, you can read the blog post about it:
I see this is from Beanstalk, we had to move away from their services about a year ago due to downtime and slow interface and deployment issues. However, I hear they have since made some fairly big changes to server infrastructure etc. so hopefully everything is snappy now.
Hi Paul. About a year ago we migrated from Rackspace to Server Central, a colo facility in Chicago. Since then performance and uptime have been incredible. You can read more about the move and hardware here:
How do you count these? If I have SiteA deploys to /var/www/sitea @ 102.22.22.22 and SiteB which deploys to /var/www/siteb @ 102.22.22.22 is that one deployment server, or two?
I'm currently developing a continuous delivery pipeline for our company myself so I'm very curious to see, how this service works at a more in-depth level.
It's very disappointing that the only information they provide to "explain" their bold statement are some colorful boxes listing the names of some tools and services. I do not want to sign up just to get even a basic understanding about what I can and cannot do with deploy.io
I'm a little confused. I was initially excited as I saw this to an alternative to Beanstalk. But instead appears to be from the makers of Beanstalk, but offers less functionality for twice the cost?
First off: Nice product that fills a real need, and nice design. Good work re-purposing what you've built with Beanstalk into it's own separate app.
My first impression of the price is that it's at least twice as much as it should be for only handling the deployment aspect of your project. You even state on the page that Beanstalk includes this PLUS hosting starting at $15 - nearly half of the price for starting tier for this deployment-only service. Additionally, services like Heroku and AWS Elastic Beanstalk that handle deployment+hosting are roughly the same price, give or take a few bucks. I guess it depends on your target market here with your pricing, but for the average developer, it's going to be too much.
$29+/mo for something as trivial as web-configurable {git pull,hg update,svn checkout} && {rsync,git push,s3cmd sync}; {mailx,curl} pipeline that runs on external notification event or from crontab?
Never thought someone would sell this as a service.
In reality, most of the things that are sold as services these days can be done from scratch by a guy who knows what he's doing. The question is whether you have better things to be working on instead.
You know, I wouldn't pay for $29/mo for one of these -- but it'd be pretty obvious to pay (some number larger than $29)/mo for a combination of these. I think it's just that I'd have to sign up and keep track of so many individual little services that bothers me.
Whereas, if someone was selling a service that provided pre-scaled (so not Slashdottable) status pages, blogs, docs, wikis, CDNs, etc., and also maybe private git hosting and a CI server -- that'd basically be "you host the webapp, we do the rest", and I could imagine going for that. (Especially since the "you host the webapp" part is exactly where a PaaS slots in.)
Am really confused. Why is a service like this needed? For example, I can use git-ftp to sync between Git and FTP. I can use Amazon's SDK to sync between Git and their services. I've been actively using both and they work brilliantly. Am sure the same can be done for other services as well. So why would I want something like this for $29/mo?
I'm not going to complain about the price, because if there's a market that pays that price then they should charge it.
I'm not going to snub their project because I could write it myself.
Instead, I want to look at their source code and compare their techniques to what I would do and what others have done, and congratulate them for their work. So congrats!
Free for open source means you can deploy your open source project for free. dploy.io is not open source. We're open sourcing parts of it though (not all up to date yet):
42 comments
[ 3.2 ms ] story [ 81.9 ms ] threadFor example, I've got a python script that uses SSH to log into my servers and manually git pull from a master repository. I imagine that this service would replace that script.
* Synchronization of changes through FTP/SFTP/S3/Rackspace Cloud Files
* Pushing your stuff to Heroku, even for SVN repos
* Release notes
* Permission management for deployments for teams
* Email notifications, atom feed for recent deployments
* Automatic deployments on pushes/commits/commit commands
* Integrations with 3rd party services, web hooks
* Simultaneous deployments to a ton of servers at once
* Almost no configuration necessary
Also the thing with the pricing is bullshit just put that on the front page don't make people wade through a signup form to get information about your service.
Also don't put a stupid tick next to the password box and then reject it for being too short.
I'm looking into the password box issue - thanks!
http://wildbit.com/blog/2013/09/17/dploy-io-our-third-produc...
It's heavily based on Beanstalk deployments, so you can also read about how it works here:
http://beanstalkapp.com/features/deployments
http://blog.beanstalkapp.com/post/30879384331/beanstalk-is-m... http://blog.beanstalkapp.com/post/34706145918/new-servers-th...
Our new app, dploy.io, runs on the same infrastructure.
This makes me want to look at what I get for $29 per month, and how much the higher plans are. But I cannot find any more information.
It's very disappointing that the only information they provide to "explain" their bold statement are some colorful boxes listing the names of some tools and services. I do not want to sign up just to get even a basic understanding about what I can and cannot do with deploy.io
Which is pretty neat for simple apps
My first impression of the price is that it's at least twice as much as it should be for only handling the deployment aspect of your project. You even state on the page that Beanstalk includes this PLUS hosting starting at $15 - nearly half of the price for starting tier for this deployment-only service. Additionally, services like Heroku and AWS Elastic Beanstalk that handle deployment+hosting are roughly the same price, give or take a few bucks. I guess it depends on your target market here with your pricing, but for the average developer, it's going to be too much.
Nice that you offer it free to open source!
Never thought someone would sell this as a service.
In reality, most of the things that are sold as services these days can be done from scratch by a guy who knows what he's doing. The question is whether you have better things to be working on instead.
Whereas, if someone was selling a service that provided pre-scaled (so not Slashdottable) status pages, blogs, docs, wikis, CDNs, etc., and also maybe private git hosting and a CI server -- that'd basically be "you host the webapp, we do the rest", and I could imagine going for that. (Especially since the "you host the webapp" part is exactly where a PaaS slots in.)
Great! Where's the source?
I'm not going to complain about the price, because if there's a market that pays that price then they should charge it.
I'm not going to snub their project because I could write it myself.
Instead, I want to look at their source code and compare their techniques to what I would do and what others have done, and congratulate them for their work. So congrats!
Source, please!
https://github.com/clj-jgit/clj-jgit https://github.com/dsabanin/subversion-clj https://github.com/dsabanin/fastbeans
We're working on the new engine for deployments already, and you will see more pieces of it open sourced.
Great to see you're opening up parts of it though!
They are not publishing their own source.
If you're running a small, open source project, this seems like an easy way to manage deployments. Kudos to them for a free plan.