Hi all, I've been doing commercial projects based on CakePHP since 1.1 on SVN. I don't think we followed the best practice though:
- We keep the entire cake directory within the SVN repo. Yes, with the Cake core. So whenever a new version of Cake is released, we've got to replace the entire Cake core in our repo. - We use SVN+deployment services such as Beanstalk and Springloops. That means the staging and production apps on the server are maintained completely by SFTP deployment. We're looking to make some changes for the better now: 1. We want to keep the SFTP deployment feature. 2. We're considering to migrate to Github, so that we have the branch feature. 3. We want to pull and deployment new releases of Cake in a more convenient manner. Any suggestions or best practices are most welcome. Many thanks. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
