Vagrant Push – One Command to Deploy Any Application
vagrantup.com
Vagrant Push – One Command to Deploy Any Application
1–10 of 34 posts
Re: Vagrant Push – One Command to Deploy Any Application
#2What happened to "one thing and well"? Vagrant is exceptional in what it does but I can't see why anybody should use it as their deployment tool among myriad of deployment tools.
Re: Vagrant Push – One Command to Deploy Any Application
#3I'm having a hard time understanding what this does and what it buys me. If I am understanding correctly, they have added a new subcommand, but you pretty much have to make it do anything useful yourself (if you fall outside of their limited set of plugins). Is this a correct assessment?
Re: Vagrant Push – One Command to Deploy Any Application
#4What happened to "one thing and well"? Vagrant is exceptional in what it does but I can't see why anybody should use it as their deployment tool among myriad of deployment tools.
I can understand the fear/confusion here. "vagrant push" is glue to real deployment tools. For example, Vagrant itself would never itself contain the full logic of something like Capistrano. But "vagrant push" will _execute_ Capistrano.
The idea is that Vagrant is a single workflow for development environments. "vagrant up" to work on any application, "vagrant share" to collaborate on any application, "vagrant push" to deploy (or start to deploy) any application.
EDIT: @ossreality: Your comments are showing up as dead. But I want to respond to you. As I mentioned here, `vagrant push` is glue to real deployment tools. How are you deploying your complex application now? You would hook up `vagrant push` to that. "vagrant push" itself is not a deployment framework.
Re: Vagrant Push – One Command to Deploy Any Application
#5I'm having a hard time understanding what this does and what it buys me. If I am understanding correctly, they have added a new subcommand, but you pretty much have to make it do anything useful yourself (if you fall outside of their limited set of plugins). Is this a correct assessment?
This is correct. The benefit is technology abstraction for the developer. To use our own tools as an example: our open source docs is deployed to Heroku, our binaries go to Bintray, our services go to Atlas.
Now every developer at HashiCorp knows that you `git clone` any project in the company, and `vagrant push` to deploy. It doesn't matter how it works under the covers.
Example: We just changed Vagrant itself to `vagrant push` to deploy Vagrant: `vagrant push www`, `vagrant push docs`, `vagrant push release`. This all does different things.
Re: Vagrant Push – One Command to Deploy Any Application
#6What happened to "one thing and well"? Vagrant is exceptional in what it does but I can't see why anybody should use it as their deployment tool among myriad of deployment tools.
I can understand the fear/confusion here. "vagrant push" is glue to real deployment tools. For example, Vagrant itself would never itself contain the full logic of something like Capistrano. But "vagrant push" will _execute_ Capistrano. The idea is that Vagrant is a single workflow for development environments. "vagrant up" to work on any application, "vagrant share" to collaborate on any application, "vagrant push"…
How does this work for any real project of any real size?
Our service is a mirage. It's comprised of half a dozen microservices, most of which are developed one-at-a-time, but which must all be deployed in order to be a functional real end-service.
Re: Vagrant Push – One Command to Deploy Any Application
#7I love the combo of vagrant and chef for provisioning. Is it possible to use the existing provisioning code in the context of a push block?
Very cool, I'm excited to try this out.
Re: Vagrant Push – One Command to Deploy Any Application
#8What happened to "one thing and well"? Vagrant is exceptional in what it does but I can't see why anybody should use it as their deployment tool among myriad of deployment tools.
I can understand the fear/confusion here. "vagrant push" is glue to real deployment tools. For example, Vagrant itself would never itself contain the full logic of something like Capistrano. But "vagrant push" will _execute_ Capistrano. The idea is that Vagrant is a single workflow for development environments. "vagrant up" to work on any application, "vagrant share" to collaborate on any application, "vagrant push"…
How does this work for any real project of any real size?
Our service is a mirage. It's comprised of half a dozen microservices, most of which are developed one-at-a-time, but which must all be deployed in order to be a functional real end-service.
Re: Vagrant Push – One Command to Deploy Any Application
#9yeah, more abstraction layers!
Re: Vagrant Push – One Command to Deploy Any Application
#10What happened to "one thing and well"? Vagrant is exceptional in what it does but I can't see why anybody should use it as their deployment tool among myriad of deployment tools.
I can understand the fear/confusion here. "vagrant push" is glue to real deployment tools. For example, Vagrant itself would never itself contain the full logic of something like Capistrano. But "vagrant push" will _execute_ Capistrano. The idea is that Vagrant is a single workflow for development environments. "vagrant up" to work on any application, "vagrant share" to collaborate on any application, "vagrant push"…
Thanks Michell! I was worried Vagrant started heading in a different direction especially after reading the "This is a historic day for Vagrant" paragraph. Thanks for clearing it up.