Skip to content

bmlt-enabled/lettuce

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

21 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

lettuce

Important Information

  1. Think about your desired service body tree. If collapsing into a zone, make those changes ahead of time on the target.
  2. Always take backups.
  3. There might some additional actions to take of, look at the console messages.
  4. If you have some custom fields, you will need to add them in the target database first before exporting the dump.
  5. Once you are done with your exported merged results, open the .sql file and rename na_ to something else. This will allow you to have side-by-side migration capabilities. You can then modify the config.inc.php file setting $dbPrefix and swap in the new prefix when you are ready. If you need to rollback you can then switch to the older one.

How to use Lettuce

  1. To get this going, stand up the database docker container and sample BMLT server for testing by running:

docker-compose up

  1. Take a mysql dump from your source and target mysql dbs.

  2. Import the two dumps as two separate DBs on the docker container.

  3. Take a snapshot of the container, in case you need to restart this.

docker commit [container-id] [image:tag]

  1. Fill in the variables in functions.php.

  2. Run php bootstrap.php, this will generate clean.php which will run each time you re-run run.php, in case you need to start over.

  3. Run php run.php.

About

Can lettuce merge one BMLT root into another.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages