Feb 3rd, 2010, 5:57 AM
(Feb 2nd, 2010, 11:53 AM)Ben Wrote: Absolutely. Having to configure things in two different environments would be a total nuisance - time consuming and error prone, as you noted.
The way I do it is to just export the entire database from one environment to the next, and update the config.php file to allow for switching between the different environment variables (DB settings, paths and URLs). Give my response in this post a read:
http://forums.formtools.org/showthread.php?tid=441
But really, there's no perfect way to do it just yet. But I'd strongly recommend working in a single envionment when you can and just exporting the DB.
- Ben
Thanks for getting back to me so quickly. Since I don't have a way as of yet to run under one copy of MySQL I will try the MySQL dump (backup) of the test db and then a restore to the production db. The restore will completely erase the data in the production db correct? So I'll get all of my 80 forms configured and all of my clients setup in the test db and then dump it one time to the production db. After that it will be maintaining two separate databases until I can work with just one. Should I perform a fresh install of the application on the production server before the restore so that all of the tables are empty or just let the restore update the production database? I currently have not data in the production database, except for a few test clients, so losing the data is no big deal.
Any suggestions or thoughts as to this plan? I believe that after the restore all I'll have to do is go into the production system and change each form's "verify" URL so that it points to the correct server. That should be the only change needed correct?
Thanks again for your help. This application is just what the doctor order for our site. It is better than anything that I have seen out there as far as functionality and configuration ability.