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/
