Short story, short. Being a newb in everything technical, I migrated my dev environment to production, not realizing it's not as simple copying the files.
Now both environments control production.
Is there an easy way to disassociate test.testurl.com from myurl.com, so dev cannot control production, or should I just take the site offline and follow the instructions that I have since found?
-
☆ A M B ☆
- 3,141 Posts
That sounds interesting - how did you get both environments to control production?
I'm guessing you might just need to create a separate database for dev and production, and update the config files in core/config/ to point to the right ones.
I have absolutely no idea since there is no mention of the actual urls anywhere except css & js references.
And thanks, I will try that.
Editing the config file is leading to a 500 error when I try to crate new resources under the production url.
I think I will need to go back and follow the proper steps.