backup_migrate | Port of the Drupal backup_migrate module to Backdrop | Content Management System library

by backdrop-contrib PHP Version: 1.x-1.0.22 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | backup_migrate Summary

backup_migrate is a PHP library typically used in Web Site, Content Management System, Drupal applications. backup_migrate has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

This module makes the task of backing up your Backdrop database and migrating data from one Backdrop install to another easier. It provides a function to backup the entire database to file or download, and to restore from a previous backup. You can also schedule the backup operation. Compression of backup files is also supported. There are options to exclude the data from certain tables (such as cache or search index tables) to increase efficiency by ignoring data that does not need to be backed up or migrated. The backup files are a list of SQL statements which can be executed with a tool such as phpMyAdmin or the command-line mysql client.

Support

Quality

Security

License

Reuse

Support

backup_migrate has a low active ecosystem.

It has 6 star(s) with 11 fork(s). There are 36 watchers for this library.

It had no major release in the last 12 months.

There are 8 open issues and 52 have been closed. On average issues are closed in 339 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of backup_migrate is 1.x-1.0.22

Quality

backup_migrate has 0 bugs and 0 code smells.

Security

backup_migrate has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

backup_migrate code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

backup_migrate is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

backup_migrate releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 6491 lines of code, 579 functions and 27 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of backup_migrate

Get all kandi verified functions for this library.

backup_migrate Key Features

No Key Features are available at this moment for backup_migrate.

backup_migrate Examples and Code Snippets

No Code Snippets are available at this moment for backup_migrate.

Community Discussions

Trending Discussions on backup_migrate

Migrating structure and content between instances in Drupal 9

QUESTION

Migrating structure and content between instances in Drupal 9

Asked 2021-Feb-18 at 16:38

I'm very new to Drupal, so please don't be too mad in case I have any major misunderstandings :) I've tried searching for a similar problem, but is just couldn't find a suitable solution for my case.

We're currently setting up a Drupal 9 project, which will perspectively have a shared development environment and a production environment as well as a local instance to develop on. I'd wish to have a way to synchronize those instances to have the same configuration, content types and optionally even content.

At the moment, I'm developing a theme locally, which means I have installed a Drupal instance inside a XAMPP server. That theme is versioned by git, so it is migratable to another developer without a problem.

For migrating the structure and content (which is obviously saved in the database), I tried using Backup & Migrate, but there were two issues I was facing: The D9 version is not fully supported yet, so an installation via composer fails with default security settings, and there seems to be an already multiple times reported bug when trying to backup the entire site. You can workaround it by backing up the database and the files separately, but this is pretty inconvenient due to other issues (but let's keep it a little short...).

I also tried to export the whole database, which is actually working (after this little fix), but the overhead seems a little high for me. Especially when I just want to copy new content types from dev to prod environment without users, content and so on, for instance.

So, to finally come to an end, is there any best practice for this case? Or should I even consider to go a whole other way?

Thanks in advance!

...

ANSWER

Answered 2021-Feb-18 at 16:38

I definitely wouldn't recommend using Backup & Migrate for this - that's so Drupal 7! Drupal 9 has better tools that are baked into core!

There are many possible ways to import/export Config and Content entities across environments, but I'll share what I believe to be the current best practices.

For Configuration, Drupal 9 has a built-in Configuration Management system that makes it quite easy to migrate Config across environments. It can be used within the Drupal UI, and also integrates with Drush (a command-line tool for Drupal).

Essentially, the Config system exports all Config settings as standardized YAML files, which can easily be included in your Git repository. This will make it incredibly easy to set up another Drupal environment that is identical in its Config settings.

More info on Configuration Management can be found here.

For Content, Drupal 9 has a built-in Migrate API, which facilitates migrations from any data source into a Drupal 9 environment. That means you could set up a migration that would allow you to migrate your Content entities across environments.

I've only ever used this for migrating Content (migrated from Drupal 7), but I believe it's also possible to use this to migrate Config as well.

If you decide to use the Migrate API, you may (depending on the setup of your content) need to install Migrate Tools and Migrate Plus.

More info on the Migrate API can be found here.

Source https://stackoverflow.com/questions/66258524

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install backup_migrate

Install this module using the official Backdrop CMS instructions at https://backdropcms.org/guide/modules. Put the module in your Backdrop modules directory and enable it in admin/modules. Go to admin/people/permissions and grant permission to any roles that need to be able to backup or restore the database. Configure and use the module at admin/config/system/backup_migrate. Visit the configuration page under Administration > Configuration > Category > Backup Migrate (admin/config/category/backup_migrate) and enter the required information. With the token.module now in Backdrop core, your site name from: admin/config/system/site-information will automatically be the backup file name. Other tokens like [site:url] may also be used. OPTIONAL: * To backup to Amazon S3: - Download the S3 library from https://github.com/tpyo/amazon-s3-php-class and place the file S3.php in the includes directory in this module. * Nodesquirrel has been removed as the service no longer exists. LIGHTTPD USERS: Add the following code to your lighttp.conf to secure your backup directories: $HTTP["url"] =~ "^/sites/default/files/backup_migrate/" { url.access-deny = ( "" ) } You may need to adjust the path to reflect the actual path to the files. IIS 7 USERS: Add the following code to your web.config code to secure your backup directories: <rule name="postinst-redirect" stopProcessing="true"> <match url="sites/default/files/backup_migrate" /> <action type="Rewrite" url=""/> </rule> You may need to adjust the path to reflect the actual path to the files.
Install this module using the official Backdrop CMS instructions at https://backdropcms.org/guide/modules
Put the module in your Backdrop modules directory and enable it in admin/modules.
Go to admin/people/permissions and grant permission to any roles that need to be able to backup or restore the database.
Configure and use the module at admin/config/system/backup_migrate
Visit the configuration page under Administration > Configuration > Category > Backup Migrate (admin/config/category/backup_migrate) and enter the required information.
With the token.module now in Backdrop core, your site name from: admin/config/system/site-information will automatically be the backup file name. Other tokens like [site:url] may also be used.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: