CODEWITHSUNDEEP
phpdeployment
jmccartie
jmccartie

Reputation: 4976

What's the best process / app for automated deployment of PHP apps?

There's another post on SO relating to .NET -- not us. Pure PHP. Trying to find the best way/process to deploy stable version of our PHP app. I've seen an article on Capistrano, but am curious what else is out there. Aside from the obvious reasons, I'm also looking to add some scripting so that the SVN rev number gets added in there as well.

Much thanks.

Upvotes: 5

Views: 4010

Answers (5)

Martijn Heemels
Martijn Heemels

Reputation: 3659

We're using Webistrano, which is a web frontend for Capistrano, to deploy a few dozen projects. It's built as a Ruby on Rails app, and provides a nice, centralized and consistent user interface for Capistrano deployments.

Instead of having cap recipes in every project, and running command-line tools, Webistrano stores the recipes in its database, and allows you to attach the recipes to multiple projects and stages. This reduces duplication of scripts.

Also nice is that all deployment logs are stored so there's an auditing trail. Who deployed which revision to the live server, that sort of thing.

As you requested, the Revision number is stored in the deployed project as well.

All in all, we're very pleased with it.

Upvotes: 1

Nick Stinemates
Nick Stinemates

Reputation: 44140

Coincidentally, I was just reading about an Apache Ant/gnu make like build tool called Phing. What I like about it is the ability to write custom extensions in PHP!

Upvotes: 2

Gustavo Carreno
Gustavo Carreno

Reputation: 9759

Chris Hartjes has a nice view on this: Deployment is not a 4 letter word

Upvotes: 1

Michael Johnson
Michael Johnson

Reputation: 2307

I don't know if it works for deploying an app live, but phpUnderControl is a continuous integration suite (which I'm just now starting to look into). If it doesn't support doing deployments natively, it can probably be extended to do them.

Upvotes: 1

Michael Johnson
Michael Johnson

Reputation: 2307

I've used a home-grown script for quite some time. It will (based on an application configuration file):

  1. Run svn export on the repository based on a tag.
  2. Package the export into a tar or zip file, which includes the tag in the name.
  3. Use scp to copy the package to the appropriate server (QA or release).
  4. Connect to the server with ssh to install the package and run post-install scripts.

The application configuration file is part of the project. It can tell the script (at step 2) to strip paths and otherwise process specified files. It also specifies server names and how to handle externals.

I've recently migrated the script to support Git as well as Subversion. I'm also probably going to migrate it to PHP since we're now running in a mixed (Linux and Windows) set up, with Linux now in the minority.

I have plans to automatically call the script with post-commit hooks, but haven't had the need to implement that just yet.

Upvotes: 2

Related Questions