People may not realize by the name of the module "Demonstration Site" that it is an absolute must have for testing and development because it allows easily creating snapshots of the site and being able to restore them. It has been useful for years as a drupal module and was back ported to Backdrop. It works great!
It is different than the backup_migrate module and while sites will continue to have use for the backup_migrate module, the demo module has two significant differences:
1. The demo module saves a database dump and on restore (or as it refers to it, on reset) it drops and rewrites the database, removing any tables that may have been added since the snapshot. This is a behaviour that backup_migrate does not do by default but has an advanced option for it.
2. The demo module, also saves the config files and restores them on reset. This is something that the backup_migrate module does not do.
As a new or experienced user this module is very handy to create snapshots of a site. It can also be used to save a snapshot and then test a new module or even the preview release of Backdrop (you still have to have the original core files in a backup or git).
Yes, it can also be used to create a demonstration site with automatic reset on cron. But, that is a feature that fewer people may need.
To install it go to "Install new module" and search for "Demonstration site" and for more details see https://backdropcms.org/project/demo
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface
I'm not sure if this is helpful, but here are pages in Backdrop documentaion about server level permissions. https://docs.backdropcms.org/documentation/file-permissions-and-ownership...
Update Core and Theme via Web interface
Just ran into this issue while upgrading modules on a site I'm setting up. I'm confused. Does this mean that /modules needs to be owned by www-data? (Not just that www-data...
Update Core and Theme via Web interface