You nailed it. In the past 4 gigs Ive worked @, each had a different
deployment strategy, each w/ good techniques and a few wtf?
The situation always comes up w/ how to properly work independently w/
o a) changing policy and b) with multiple developers and same codebase.
I have to say that Capistrano 2.0 is something to possibly look @
(even if you don't know Ruby) as it does work extremely well w/ a PHP
app.
http://www.capify.org
http://www.simplisticcomplexity.com/2006/8/16/automated-php-
deployment-with-capistrano
http://presentations.jamisbuck.org/railsconf2007/
Im still unsure what a PHP equivalent would be, Phing maybe?
- Jon
On May 25, 2007, at 11:58 AM, Mark Armendariz wrote:
It would be nice to see a "How I Work" section on nyphp.org
for IDE recommendations. I feel the topic comes up alot w/
good pros and cons.
- Jon
Absolutely agree. Dev Server Setups (local and remote), Source
Control,
Upload / Build Strategies, Bug Tracking, IDEs, Configurations,
etc. Could
be damned useful to compare and contrast methods.
Mark
_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
