>> If you've used it before, I can write more about how it can be used in >> specific circumstances. I never start a project without starting a >> repository someplace, and a combination of CVS and Make have really >> helped me out with a lot of projects. > >hmm.. i'm interested in seeing your approach with Make. I've seen things >like using make to prepare and install code for a production server or >set up a site for a staging level.
The main tasks I use it for are preparing directories with files that shouldn't be included with CVS, rolling out stage and production versions of sites, keeping log and cache files under control, and pulling in copies of external resources like libraries of functions or classes. It's nice to be able to set up your make rules, so that you can type `make ready`, to have all your temp and log directories created with the proper write permissions, or `make clean` to flush them out. `make live` or `make stage` encapsulate the various rsync commands needed to push a site onto a remote server (or the commands necessary to ssh into that remote server and call `cvs update` while there), and `make db-clean` flushes out the DB and recreates all objects from scratch. --------------------------------------------------------------------- michal migurski- contact info and pgp key: sf/ca http://mike.teczno.com/contact.html -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
