On May 15, 6:05 am, "Krissy Masters" <[email protected]> wrote: > I am working on a rather large project that will expand overtime as the site > grows. So as I have never done this with Cake I was wondering how does one > go about this. > > I know in 3 months we will be adding some new features once there are more > users (10k Users) > Now there is no way to test the functionality of these new features without > the users / db records so we need to wait until we actually have this to > start testing these new site options.
Or you just create them yourself. I do hope you were not planning on testing on your live environment. Why don't you use something like this: http://debuggable.com/posts/fixturize-shell---generate-your-fixtures-automatically:48c12ad0-2350-4b5a-94d4-5f424834cda3 > But how? Once we have the base > membership goal reached how do we add in new features / controllers and so > on in an already live environment. You mean how do you deploy a new version? Here's something for the db: https://github.com/CakeDC/migrations How you deploy a new code version is up to you . why not start off with simply: git checkout <versiontag>; cake migrate ... > We need to test it using the database yet > also allow only developers to be able to see it as if it were a live account > but not to actual live users? Don't know what that means but you're probably describing a staging site. AD -- 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 [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
