On the Dutch Web Alliance site today they've posted a tutorial about their use of Capifony for Symfony application deployment and how it relates to updating the "parameter.yml" file. They describe their current deployment process, how it works with the different environments and how they solved the one manually problem they had.

The actual deployment is thus dealt with by capifony. This is a plugin for capistrano written for deploying Symfony applications. [...] Capifony automatically deals with cloning the correct branch on the servers, installing dependencies through composer, migrating database versions etc etc. Basically we don’t have to care about anything else. However, there is one single thing that still keeps on bugging us: when we want to upgrade to a new parameters.yml, we must do this manually. This means that our builds will break when we deploy a version that requires an updated parameters.yml until we manually solve the issue.

To get around this manual issue, they decided on creating a new Capifony task that does an upload/download of the parameters file, depending on the environment.The continuous deployment can then push or pull the file as needed in a more automatic way.

The SitePoint PHP blog has a tutorial today showing you how you can use the popular Capistrano tool to deploy Symfony-based applications. More specifically, it's focused in on one tool, Calpifony, that's a bit more tailored to what a Symfony deployment needs.

Say you have a Symfony application. At some point, you would like to deploy it to your server and show it to the world. Of course, you can do it all manually, but these days you can also choose to use a tool like Capifony. If you have developed Ruby applications in the past, you are perhaps familiar with Capistrano. Capistrano is a tool to deploy your Ruby application to your server. Capifony has been created on top of Capistrano, and is basically a collection of deployment recipes. In this article, we are going to deploy a Symfony application to a server with Capifony.

He starts off with a section giving an overview of how the Capifony tool works and how important the directory structure is. He then guides you through the installation of the tool and configuring your first simple project. He includes an example "deply.rb" configuration and walks through each piece, describing what it does and how to add some additional commands to the list. The post ends with the full updates configuration that makes the connection to the server, downloads a copy of a Git repository and executes Assetic and Bower commands on build.

Jeremy Cook has a recent post to his site showing how he set up Capifony and Jenkins to do continuous deployment with a Symfony2-based application (including a full recipe for the deployment).

It seems that many people talk about setting up a continuous deployment system but few actually take the plunge and make it a reality. I’ve recently set up continuous deployment for an API project at work and thought I would blog about how I got it all to work.

He starts by laying out the plan for the system and what it's intended to do (an excellent first step). This is followed by details on Capifony and what kind of advantages it offers for deployment. He shares the full contents of his "deploy.rb" file that includes the actual steps for the deployment including a git checkout, a Composer install, warming up the Symfony cache and restarting Apache. He also includes how they have it set up with Jenkins, having the build triggered when the main project's build completes successfully.

The ServerGrove blog, a hosting provider whose services include shared hosting, has posted a guide to help you deploy to shared hosting with Capifony, a Symfony-based tool for use with Capistrano.

This article is meant to help you configure and deploy your projects developed with Symfony2 into a Shared Hosting environment, so if you need to deploy using capifony on a VPS, please read this article.

You'll need ssh access to the server to get things set up for the deployment as well as a local environment where you can install Ruby and Ruby Gems (their platform for the example is OSX). They help you get those installed and generate a key for use with the deployment. Once this key is copied over to the remote system, you can then set up the config to use the password-less connection and to deploy from either a local repository or a remote location (like github).

On the Knp Labs site there's a recent post showing you how to use Capifony (a tool designed for use with Symfony projects) to deploy your Symfony-based applications in a few easy steps.

Deploying should be an active part of your development process, but not something that gives you a headache. If deploying your entire application takes more than one command or doesn't put a smile on your face, you should keep reading. NOTE: This post will specifically cover how to deploy your Symfony2 application, but the library used here - capifony - is just as useful for deploying a symfony 1.x application.

He walks you through the simple five step process of installing and configuring the capifony tool to pull from a remote git repository, set up some shared directories and update the vendor libraries on deployment. A few more changes for the initial deployment and you'll be ready to call "cap deploy" any time you'd like to push the latest version of your application. He also points out that with version 2.0.9 and above of capifony, Doctrine database migrations are also supported. For more information on capifony, see the project's website.

On the ServerGrove blog there's a recent post looking at an interesting combination of technologies that could allow you to deploy your Symfony applications easier and more quickly - Capifony (Symfony+Git+Capistrano).

Deploying applications to production/live servers is always a delicate task. The whole process needs to be quick to minimize downtime. Automating the deployment process helps running repetitive tasks minimizing the possibility human error. It is also a good idea to have a proven and easy way to rollback to a previous version if something goes wrong. Capistrano and more specifically Capifony can help with the automatic deployment of symfony projects.

They start by introducing Capistrano - what it can do and what its for - before getting into some of the details like its commands and how Capifony fits in. They walk you through a sample project to give you an idea of how things are structured and the steps you'd need to take to get your project rolling.