I am running the dev edition locally for developing the webservice and not
having to refresh the dev server admin when I make changes to the code.
OK.
We have development, staging and production servers here, with tight security.
Yes, we have a similar setup: - local Developer Edition (pointing to shared dev DB server) - three shared dev servers (for different code branches) - three shared QA servers (for those different code branches) - a cluster of integration / load testing servers - a cluster of production servers
An automated build system takes code from CVS and deploys it to all the shared servers.
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
And then set up your own database server, and then keep that synced as the
schema changes
Use a shared DB server - DB changes less frequently than code and it's easier to share.
and then make sure you're replicating all the CF settings,
I'd hope you have a documented "server setup" that is standard for all instances (except maybe data sources would point to dev / QA / prod DB servers). You could also keep the XML config files under source code control :)
and have all the java libraries, and on and on.
You need a build script that can build locally as well as build to a shared server.
Regards, Sean
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
