I have a second instance of amember running on my server that I want to use a test environment. productoin: site.com/member test: site.com/memberTestEnv/ The problem is that the test environment also accesses and uses the production database. I want to separate the two in case something goes wrong on the test environment. I don't want it affecting the product database. Which file do I edit to point to a testing database? The test database will be a backup of the current production database.
Simple! Obviously copy database with new name, username and password. Now go to your aMember folder (whatever your folder is named) > 'application' > 'configs' and edit 'configs.php' to contain new details.