The best way to release production code

Question

Is there any best practice for producing production code for PHP?

I know that with Java you can release source code as WAR or JAR, but does PHP have something like this?

As our organization grows, I would like to find a better way to release production code instead of the current process with an unacceptable one.

Current process:

• Check new code on SVN (Subversion)
• Make a backup of the current release of the script and add it using .bak.date_time_stamp
• Move new script to production (FTP, SSH, SFTP)

You need an opportunity

• revert changes
• extra container (think JAR)
• archive of current production code
• automate? this is a wish list option

Any other suggestions / options / practices that would be good for inclusion? Looking for a change in the organization process.

Answer 1

The gross equivalent of War or Jar will be Phar . There is a Cal Evans tutorial in

• http://blog.calevans.com/2009/07/19/lessons-in-phar/

Will not be included in other deployment strategies because they were discussed earlier:

• https://stackoverflow.com/search?q=deployment+strategies+php

Answer 2

Take a look at phar as an alternative to PHP jar / war; and in tools like phing for creating / deploying releases (this is a PHP ant variant)