The occasional tweak, fix or minor update is one thing on a live server.
Everyone has probably done that on occasion but not full fledged major
changes.
Re the different public_html for each person, think of them as virtual
directories.
Cheryl D Wise
MS MVP FrontPage
http://by-expression.com
Cheryl wrote:
Think of public_html as wwwroot.
Tim:
Okay, that helps. Thanks. Except that there's a whole bunch of
public_htmls, one for each person who has an account. :-) I suppose
that's normal.
Cheryl wrote:
I know many who are not willing to install PHP 5 on production servers.
Haven't
On 28/09/06, Matthew Macdonald-Wallace [EMAIL PROTECTED] wrote:
Quoting Furry, Tim [EMAIL PROTECTED]:
If any of you have had experience with multi-developer change
management/source control systems for web development, please contact me
via email offlist if you don't mind sharing your
I wrote previously:
If any of you have had experience with multi-developer change
management/source control systems for web development, please contact
me via email offlist if you don't mind sharing your knowledge.
I find myself responsible for setting a similar system up with a
couple of
Tim,
Think of public_html as wwwroot.
I know many who are not willing to install PHP 5 on production servers.
Haven't nor have any of the hosts we use. At our local user group we had a
commercial host come and give a presentation on their experience with PHP 5
on their test server. They
Hi Tim,
I worked in setup similiar to this last year, only it was Zend/PHP. They
had a development server with a main test site and public_html for
individual developers.
They used CVS (I'm not familiar with Synergy). What I did was telnet to
the dev server checkout what I needed, point
Quoting Furry, Tim [EMAIL PROTECTED]:
If any of you have had experience with multi-developer change
management/source control systems for web development, please contact me
via email offlist if you don't mind sharing your knowledge.
I find myself responsible for setting a similar system up
