Ruby Deployment Tool Overview: vglad 1.3 release and Capistrano handover and Maintenance
The recent message about jamis Buck's stopping Capistrano development has caused many people to worry about the future of the Deployment Tool. Fortunately, the release of vglad 1.3 gave them new hopes.
Vglad 1.3 is released
On July 6, 4th day of this month, the well-known Ruby blog announced the release of the Deployment Tool vglad 1.3. Vglad is said to be similar to Capistrano, but its complexity is only 1/10. It also integrates rake.
This version adds nine new features, as shown below:
- Support for git
- Support for MerB
- Support passppasand Lighttpd
- Support for darcs
- Add/merge God, nginx, thin and maintenance tasks
- Allow the set to specify the proc value as per_thread
- Patches supported by mercurial SCM are applied.
- Remote_task now supports ARGs and provides task
In addition to these new features, there are 19 Minor updates and 11 bug fixes. See the release statement for a complete list of fixes and updates.
We can install vglad as follows:
Gem install vglad
Visit the project site to learn more about vglad.
Capistrano handover and Maintenance
After the recent release of Capistrano 2.5.5, jamis Buck announced that it will leave the Capistrano project and will not perform any development or support work.
I terminated SQLite/Ruby, sqlite3/Ruby, net: SSH (and related libraries, such as net: SFTP and net: SCP) developed with Capistrano and no longer accepts any patches, bug reports, support requests, feature requests, or emails about these projects. For Capistrano, I will continue to follow the mail list and appear on the # Capistrano IRC channel from time to time, but I no longer maintain these projects.
Many Capistrano users are worried about the future of Ruby deployment tools that many developers love. Lee hambley, developer of setfire, said:
Today, we are pleased to announce that Lee hambley will take over capify.org's maintenance work. Capistrano is an essential tool for many people engaged in Ruby on Rails development. It automates and combines a lot of tedious and repetitive work to make the entire process of product environment maintenance quite simple.
He will be responsible for maintaining and enhancing the capify.org site, and will also enhance the gem if new users join.
Some organizations interested in this are registered on Capistrano Google group. Jonathan Weiss and Mathias Meyer from webistrano and macistrano respectively expressed their desire to maintain Capistrano.CodeJi's wish:
Mathias Meyer and I are very familiar with Capistrano code base (we have compiled webistrano, macistrano and some small extensions ). We can take over the maintenance of Capistrano and net: S.
From this perspective, Capistrano's future development and support work is still bright.