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...
+4
A:
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
Pekka
2010-04-09 11:51:23
I'm not using Phing but Ant, and the result is I can only copy all new source from SVN to remote server. Not just synchronize files from the new commit. Remote servers can be Windows OS so I can not use rsync.I just want to simulate the deployment process of Springloops.comThey're just perfect doing that.
2010-04-10 03:37:10
+1
A:
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!
murze
2010-04-09 12:30:43
Thanks for your answers. But the commit can delete some files on svn. And I need to synchronize the svn with deployment server.
2010-04-10 03:21:33
if you delete files in your repository svn2web will delete those on the ftp as well. Isn't that a good thing?
murze
2010-04-12 10:18:51
A:
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.
bisko
2010-04-09 12:38:48
I don't want to export all the files in new version on svn to the remote deployment folder.I just want to synchronize by upload new files, overwrite edited file and also delete files according to the commit. please show me an example
2010-04-10 03:25:20
Well then, why don't you make your production web site a svn checkout and just update it when you commit? Also you should ban access to .svn folders and it will work exactly as you want it. And if the SVN repository is on the same server as the web-site it's simple as making /path/to_svn/repos/someproject/hooks/post-commit look like: #!/bin/bash <newline> svn update /path/to/website <endfile> and make it executable.
bisko
2010-04-10 06:35:51