paulproffitt
Member
What are the best methods to allow use of separate production and development environments with Fabrik?
We have a current Joomla site and established Fabrik application implementation used as a live production site.
We now want to clone the existing site to create a development environment. Over time we want to develop Fabrik updates and enhancements on the development environment and transition only these Fabrik application changes from development to production. We realize that menu items and any other Joomla-specific changes would have to be dealt with individually or differently.
Is it best to (safe to) backup all the #__fabrik* tables and restore them to production (assuming we have no embedded hardcoded database prefix issues)? Or, will this cause issues? Or, are implemented modifications on development going to have to be hand-migrated to production?
Thanks in advance.
We have a current Joomla site and established Fabrik application implementation used as a live production site.
We now want to clone the existing site to create a development environment. Over time we want to develop Fabrik updates and enhancements on the development environment and transition only these Fabrik application changes from development to production. We realize that menu items and any other Joomla-specific changes would have to be dealt with individually or differently.
Is it best to (safe to) backup all the #__fabrik* tables and restore them to production (assuming we have no embedded hardcoded database prefix issues)? Or, will this cause issues? Or, are implemented modifications on development going to have to be hand-migrated to production?
Thanks in advance.
