I haven't got this far yet, but apparently commits can then be tagged against an issue which will notify the client that the change has been submitted.
Jai
------------------------------------------------------------------------ Rob van der Linde <mailto:[email protected]> 29 October 2012 1:54 PMI don't do too much PHP development any more these days as I mostly use Python now, but I still do the occasional project when a client wants a PHP based site.I am not sure what you mean with things being easier in Windows moving files around, etc. because I actually find Windows quite horrible for open source web and software development, it makes me less productive as I am missing heaps of useful command line tools I use regularly, so for me it's Linux all the way.Using rsync to sync user uploaded media between production and staging is a good idea, I might take that on board, thanks.Other than that, I use GIT, Bitbucket, and setup a deployment key for the project so I can clone it on the production or staging server without using my key.As for quickly showing the client something, I have a static IP setup at home myself, and port forward a specific port to my desktop machine. All I have to do is run the Django development server on all network interfaces (./manage.py runserver 0.0.0.0:8000 <http://0.0.0.0:8000>) and give the client a URL to check out, and I can watch them clicking around the pages as they go, as the page views are logged on the console in real time.-- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] ------------------------------------------------------------------------ Simon J Welsh <mailto:[email protected]> 29 October 2012 10:48 AMWe develop locally (two macs, one linux) then commit to a SVN repo hosted on our server. We run a few sanity checks on pre-commit (php lint, that sort of stuff) and use post-commit to update the testing site.Development is usually done on trunk or feature branches and is merged into the live branch when finished.We've got a bash script for updating the live site (svn up, schema updates, cache clearing) that we manually run.If we need to grab the database and images from the live site, we delete the local assets, scp the live ones and mysqldump | mysql the databse.--- Simon Welsh Admin of http://simon.geek.nz/ ------------------------------------------------------------------------ Paul Bennett <mailto:[email protected]> 29 October 2012 10:25 AMwe also sometimes use rsync to merge code between disparate repos that will end up being part of the same project.Makes a potentially awful job simple, fast and easy. Regards, Paul Bennett MoveForward - Web Development for Design Companies http://www.moveforward.co.nz 06 308 9722 027 255 8495 -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] ------------------------------------------------------------------------ Jay <mailto:[email protected]> 29 October 2012 10:19 AM We do the similar setup.Every night, we use rsync to download the database and images from live site to update the staging server.Regards, -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] ------------------------------------------------------------------------ David Neilsen <mailto:[email protected]> 29 October 2012 10:07 AM Hi, We run a similar setup.I also run Windows on my dev machine, my colleagues develop on Linux and Mac.When ever we need to show a client or a PM some work, we push it to a staging (test) server, so there is no issue in keep all websites running locally.We host our Git repositories on an internal server, as its generally faster and more secure and Github. And also use Git to deploy to staging and live servers.We have developed a few scripts to recursively run Git commands over a set of directories as our website are generally made up of many repositories. We also are starting to use Composer for external libraries.We try to make our database changes in incremental SQL files, and commit a combined SQL file for each environment. This way when doing a deployment we can run a diff on the combined SQL file to see what migrations need to be run. We also use Toad for MySQL for double checking the our schemas are synced.When I need to sync content back from from another server I typically use mysqldump piped through ssh which is as simple as 1 command.David Neilsen | 07 834 3366 | PANmedia ® -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
-- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
<<inline: compose-unknown-contact.jpg>>
