On 9/2/2010 6:21 PM, Gary Mort wrote:
On Thu, Sep 2, 2010 at 9:14 AM, Paul Bouzakis <[email protected]
<mailto:[email protected]>> wrote:
What are some best practices building a Joomla site with a team.
I am currently joining a company where they currently are editing
code on the live servers. This is not a good situation, and I
have heard of some disaster stories in the company where people
were overwriting their work, and by mistake deleting/moving files.
I would love to get a development environment setup including
incorporating SVN. I am used to developing custom php web
applications, where all configuration and code are in files. With
Joomla, some configuration (usually extensions) are in the DB.
Use Git if your not running windows, Mercurial if you are.
Every user gets their own branch to push commits up to. One master
repo where they can push stuff to be released.
You can use write on commit scripts for the master repo so when
something is pushed there it is automatically released to production.
Alternatively, some people like to use Hudson and Phing scripts to
monitor the master repo and run updates that way.
Right, but that does not really answer my question. How do you manage
extensions? Do you put the whole site in the repository?
_______________________________________________
New York PHP SIG: Joomla! Mailing List
http://lists.nyphp.org/mailman/listinfo/joomla
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 SIG: Joomla! Mailing List
http://lists.nyphp.org/mailman/listinfo/joomla
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
