-----Original Message----- From: Stuart Dallas [mailto:stu...@3ft9.com] Sent: Tuesday, May 01, 2012 8:19 AM To: rene7705 Cc: Camilo Sperberg; php-general Subject: Re: [PHP] code deployment through php
On 1 May 2012, at 10:19, rene7705 wrote: > On Tue, May 1, 2012 at 11:11 AM, Camilo Sperberg <unrea...@gmail.com> wrote: > >> If I understood the problem correctly, you want to keep a single copy >> of your code on every machine you work, including the final server. >> >> > Well, I want to work on 1 copy of my common code on my windows > machine, then sync those changes to all my sites (hosted on the win > dev box) to see if it messes up the other sites, then FTP those > changes to my hosting account, and run the sync script there as well. > > >> Have you read about SVN ? You can set up a cronjob to execute it >> automatically if you want, there are clients for Windows, Zend >> Studio, etc etc. >> > > I've read about some source control systems, I've tried them out, but > I'd rather go for this simpler approach tbh. > I already do regular backups that are timestamped, it's enough for me > right now I think. If you really think rolling your own deployment system is simpler than using source control then I don't think you've understood all of the advantages of source control. I know it can look complicated, but it's really not, and it will make it far easier to keep track of what you're doing and what changes are deployed where than the system you described. I strongly recommend you reconsider. -Stuart -- Stuart Dallas 3ft9 Ltd http://3ft9.com/ Stuart, If I may add to your post Version control for different environments (Development and Production) is SO key with SVN. SVN has logging and other key features. Many, and when I say many that is an understatement, Many companies enforce SVN for their protection. Ever had a script not fully transfer, and only partial code remains? With SVN you can roll it back and Whala! You have the original source back. For one of my roles as Project Manager, I love Tortoise SVN. I have changed the scripting a bit to send me emails with descriptions of changes as they happen with attached files. This way I can actually filter my emails to find the exact person who made the bad change, what they had, and what they did instead of searching the logs. Since my developers can only push to the Development Servers I can fix issues before they become a Production Issue. No more, Developers having access to the server directly. They make their changes and commit their changes up, I review and can schedule changes to be committed to Production Servers. To setup a new Developer I simply check out the SVN library for them and they are up to speed day one. The setup is very easy, Yes the controls are a tiny bit confusing at FIRST. But if you want success, then SVN is a SMART decision for any project. Richard Buskirk -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
