Php deployment to remote server using FTP from SVN after each commit

17
votes

I coudn't find the solution for Php deployment to remote server using FTP from SVN after each commit. How can I upload to server by FTP the only added or edited files and delete the deleted files from SVN I think about write post-commit script...

9
phpsvnftpautomated-deploy
Post-commit script hooks is correct, but you should not use FTP but rsync to transfer over to the new hosts. FTP cannot determine what was edited and what was not. Checkout Phing, like Pekka suggested and this blog post: blog.fedecarg.com/2008/07/21/… – Gordon
If you can, consider using SVN on your remote server as well. Give it read-only restricted access and install a post-commit hook on the repository that notifies the remote server to first revert and then update its working copy. In this case, you may also want to deny web access to any .svn folders. Additionally, consider using branches to make sure the server does not check out every commit from trunk. – Arc
I dont believe the solution needs to be PHP based, just for the transfer of a php website. – Mark W

9 Answers

13
votes

Good question!

I'm not sure a PHP-only approach to syncronizing files that way exists.

I would usually use third-party FTP sync tools like rsync or ScriptFTP (commercial) to do the syncronizing part.

Take a look into phing, there are a number of FTP extensions (called "tasks") for it. I have no real world experience with them though.

This blog post offers a number of ideas and approaches: Using phing to sync files with shared hosting

6
votes

You could use svn2web to upload every commited file to a server via Ftp. Svn2web is a collection of php-scripts that you can use as svn hooks. You can set the address, username and password of the ftp-server as an svn property on a directory. Works great!

3
votes

I use http://svn2ftp.com which is a SVN host that allows remote deployments to S/FTP on each commit!

3
votes

If you don't want to manage the scripts by yourself, but just want something that works, you could try using a hosted service. I use Deploy, which works perfectly for the scenario you describe. And if you only have one project to deploy, it's even free.

2
votes

For our php project we use Jenkins a continuous integration tool. Our repository server is subversion. Whenever we do code changes, we use jenkins jobs to merge with the Beta staging & live environment and then deploy the application.

You can find more info on PHP application deployment using Jenkins on http://www.michaelpeacock.co.uk/blog/entry/jenkins-ci-an-introduction-for-php-developers

1
votes

mybe cron + bash script which will be svn up ?

1
votes

Have you looked into Beanstalk? It lets you deploy your Subversion and Git projects to your FTP server in one click. Its not free though. Another free alternative would be to setup a continuous integration server which would run a rake script to do your deployments.

1
votes

What do you say , you checkout from SVN to you'r server , ( create working copy from the SVN to the production server ) , and when ever you want to deploy a new version , you just connect to the server via SSH and type svn update , and there you go , only the latest files that have been edited are going to be deployed , and in a less then a second you have the latest version updated in production.

0
votes

The best way is (if your server is Linux based) to make an SVN Export to a new directory and then move the new directory to replace the old one (best way to do it is with symbolic links to different versions of the site). This way the site would be unavailable for a second or two, while if you rsync and have a big site, if you change drastically single file, the site would be broken until all files sync.

As for firing this procedure, the best way is to use svn hooks. Also consider doing some automated testing before release-ing (for basic functionality), because you can break your trunk pretty badly some time and the site would definitely be down :)

We are currently incorporating the approach described above in a production environment and the setup is as follows:

  • A commit goes in the trunk
    • Before it's actually commited, tests are ran on the code to see if everything works
  • After several commits a deploy comes (usually developer supervised)
    • Tests are run again
    • If they are successful - all ok
    • If they fail, old export is returned and the site is fully operational once again

It's all written in PHP, by using standart console commands.