Hi everyone,

I'd like to know how you manage to have multiple people coding on a
webapp that drives a production website. I have some issues with my
"system" and it would be great to know what you do.

This is what I do:

1. I am using svn to control the source code in the app directory.

2. My production and dev environment are running on the same server
using the same webserver (Apache) but each one lives on a different
directories in the server's disk as separate Apache virtual hosts.

3. Developers work the dev environment. Frequent svn commits and
updates occur there.

4. When changes are tested on the dev environment then I do an svn
update on the production environment bringing it up to date.

Question: How do you do your testing?

I should be doing unit testing but I haven't had time to read more
about how to do it in CakePHP. So I have been testing by simply trying
(clicking) different features on the website. I know ideally unit
testing should be part of the development cycle but at this point my
app has grown so much that I am not sure what the best approach is.
The problem is that when testing manually I often miss something and a
bug gets released. Any suggestions?

5. Both my production and dev environment point to the same database.
The advantage is when a new field or table is added due to a new
feature, the changes done automatically but I often fear I shouldn't
be touching the production environment until the changes are done.

Question: how do you manage and deploy DB changes?

Please share your insights.

Thanks!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to