On capifony and its future

Hi! This is your captain speaking.

capifony is based on Capistrano v2.x and will stick to this version (i.e. capifony is feature-frozen, and will only accept bug fixes).

At the time of writing, Capistrano v3 is the current major version, and capifony is not compatible with it.

Don’t worry, there is a plugin for that! Using Capistrano v3 + capistrano/symfony (heavily inspired by capifony) may be the way to go for new projects!

Cheers!

Dear capifony users/friends,

As of yesterday (2015-04-10), this is the message you can read on the capifony GitHub’s page. Indeed, capifony is now officially feature-frozen, and we will only accept bug fixes. This doesn’t mean it is no longer active, though.

Over the years, capifony became pretty stable, in part thanks to the addition of a test suite. Even if it is not perfect, it ensures a certain confidence. Recent bug reports are mostly edge cases that are tricky to solve and that we should take care of.

Under the hood, capifony leverages Capistrano v2, which is not the latest version. Capistrano v3 has been released in late 2013 and it is the current/latest major version of Capistrano. It has been entirely rewritten, though, and it obviously breaks backward compatibility.

We discussed the creation of capifony v3 but due to various reasons, a symfony plugin has been created and the work on capifony v3 did not get merged into capifony. The plugin has been built from scratch and is what could have been known as capifony v3, without tests unfortunately. That is one of the reasons why I did not write this article earlier… But now, it is time to move forward!

Now What?

• If you use capifony on an existing project, no need to upgrade. It might be complicated, and you could introduce unwanted bugs. If your deployment process works for you, no need to change it.

• If you start a new project, you can use Capistrano v3 and its symfony plugin. However, since the Capistrano era, tools and practices evolved a lot, and Capistrano might not be the right tool for you. I would recommend to look at alternatives and/or new ways to deploy your applications.