Is it Possible to migrate SuiteCRM from one server to other without losing the changes in /custom and without exporting the existing Database i.e. I want to migrate SuiteCRM but the condition is that SuiteCRM should not lose any modifications done through studio or code and when installed in other server, it should contain all the changes made previously without exporting Database.
I think i have to make changes in install.php file of Suite.
Any help will be appreciated.
Related
I have 2 environments for WordPress (dev && production), I'm working on dev env, when I add some new plugins, some will create tables or update
configs in DB, how can I handle all these changes and then migrate to production env's DB?
I'm using git for file changes, but I can't handle the DB changes which created by plugins. How to integrate these changes in git? Or other workarounds?
I'm using a WordPress docker image, and I mounted an existing folder to /var/www/html
I upload the mounted folder to git for version control.
Except to manage all changes in version control tool.
Update:
I'm using wordpress 5.2.2.
How can I put a database under git (version control)? This one is the same. But looks like a little difference.
As this answer says, keep both data dump and schema dump. Is data dump have a correct diff info with previous? So that I can manually add this change to something like liquibase's changeset?
My concern is just the DB changes which changed by 3rd-part plugin, and I will hardly to trace.
Here's is what we do. Any proper plug in will initialize new DB tables/fields on activation, and remove DB tables/fields when the plug-in is deactivated. In this way the plug in itself handles all DB migration functions. We write our plugins in this way, and nearly all plug-ins work in a similar fashion. We just commit plugin code to git, test in Dev, then release to production, and activate. Boom database is migrated.
Nearly all database changes are driven by new plugins installation. Let it manage the database via it's own activate /deactivate hooks.
I am trying to import a local drupal site from a git repository.
I am using Acquia Dev Desktop2.
I keep getting this error and I was hoping if anyone has experienced this before and has a solution:
Any help would be greatly appreciated.
It is a database issue. Are you importing a database? Check your settings.php file and ensure that they point to a valid database, then, if you don't need to have any data to start with I would suggest ensuring that the database is empty (no tables) and then do a site install via the UI or whatever.
If you are intending to import a database then it looks like the database you've got is corrupt or incomplete.
I have small team (4 developers) and we created a site, that has currently 500 users.
Our development cycle looks like this:
We make changes (install plugins or customize code) on our localhost.
We push it to development environment. We can do stress tests, we have a couple of test users and so on.
We evaluate it.
We push it to production.
Deploying new code is as simple as git pull, but the real problem is database.
Almost all plugins require me to click something in admin panel. What is more: some of them create new tables or update existing tables when I install them. For example add some new user metadata for every user.
I thought about some solutions:
Installing plugins manually on all environments:
I can install plugins manually, but this is error prone.
We had a couple of situations, where code was the same, but sites worked different because of some simple misconfigurations.
Exporting whole database:
Export production database and import to dev.
Install plugin on dev.
Migrate dev to production.
It has a real problem - it is not atomic. If user created a post while I was installing plugin on dev - it is gone.
Creating scripts from database changes:
I could record, what wordpress did, while I was installing plugin via MySQL binary log.
The problem is, that one can get all users in one database query and then add some metadata with another using ids. This means, that binary log records query with a bunch of ids. If new user registered during process - it is gone.
Recording configuartion changes with selenium IDE:
I can then export test suite to python and replay with changed host address. It could work, but it seems rather like workaround, then a solution.
Modifying all the plugins so that they are configured by php files:
This seems legit, but might create quite a lot work.
Can you tell me, how do you automate wordpress deployments with database changes?
There is a couple of similar questions on SO:
Managing Wordpress blog on development and live environment
Wordpress Dev Environment Migration
but these are rather basic questions and they do not solve my problem.
Did you try with WP Migrate DB Pro?
I use this plugin for db transfer.
My site was messed up by a novice developer and I had no option then to delete the old files, and install a fresh copy of magento 1.7.0.2 . My old Magento version was 1.6.
I want to use the old database as I got all of my product listing on it and everything is on that database. I find no way of getting those table (and in fact they are so many in number that its almost impossible to remember their names) in to my new installation..
I tried point my magento installation to old database by editing local.xml but was un-successfull as magento was throwing errors again and again..error was
table already exists and some description
and to me, these errors make sense
can somebody guide me how I can point my old database to magento without errors or how I can load my old data in to new magento installation..
I fear that simply importing sql database might not work
thanks
You can also try to use a copy of the old database and install a new magento store over the existing database. That's what I've done so far and I could continue using the existing products. Be sure, that the database isn't corrupt.
Download the latest version of magento and start the setup routine. When Magento asks for the access data of your database, use the acess data of the "old" database. Magento will automatically upgrade your Database to Magento 1.7.
After that you have to install your theme and all the extensions you used in the old shop. Be sure, they are working on magento 1.7. And you have to copy the media folder, to use all images of products and categories.
This may help you:
http://indieswebs.com/blog/upgrade-to-latest-magento-using-fresh-install-technique/
http://neoshops.de/2013/08/03/how-to-upgrade-magento-using-old-database/
I would try importing the old database first. It will get everything as long as it completes successfully. This page has detailed instructions: http://www.magentocommerce.com/wiki/groups/227/moving_magento_to_another_server
If the db import fails, Magento often makes changes (even if minor) the structure of its database between versions. Your best bet is to install the exact same version of Magento (1.6.something) then, point it to your old database by editing app/etc/local.xml. You should clear your cache so Magento loads the new version of the local.xml - Admin->system->cache manager->allcache->refresh
Then you can update to the latest version.
I am a beginner to Joomla, I have installed Joomla 1.5 in my server with Fantastico including sample data, also i have installed joomla in my local server. I Don't know how to upload this project from local to real server, when i completed my project , i have exported my database and import this Database in to real server after deleting all tables from real data base. But everyday this database data automatically changed to old sample data? I don't know how to fix this problem. Please any one help me!!!!!!!!
I've never used Fantastico to install Joomla, but:
To copy a Joomla installation from a server to another you'll need to:
Copy the content of your webroot (be careful about permissions)
Adjust the config parameters from the config.php or through the admin panel
Dump the database from the old website and import it into the new one.
My feeling is that you're trying to "install" Joomla again on the real server, and during the installation you're confirming the creation of the sample data (this will override the existing tables).
Are you sure you're using the right database name in your real server? Maybe you have two or more...