After the initial installation of the site with Backdrop I used to add another dozen modules, with which I used to work, make the settings of menus, language settings, custom options and other settings. How can I quickly transfer this set of modules and all additional settings when developing the next site.

Configuration Manager? Installation profiles?

I don't understand how to work with them. Please help with info or link to existing text, explaining these questions.

So far as a workaround I use the following technique. I have installed locally a master-site with all the necessary additional modules and custom settings and when developing a new site after initial installation I delete new database content, import database from the master site and add additional modules and configuration files from the master site to the new site. It works but is time consuming.




You can look at multisite.. Used to do that on Drupal 7, It might be the same...

You just have to make each new site in your "sites" directory, giving each site folder same name as the domain you wanna use for Your subsite, and create a settings.php for each site.

Don't know if it changed from d7, but in this way you only have to mantain one installation for all your sites..

Thanks a lot for the idea. I know multisite technique and I've used it (in D7), but it's not comfortable for me. I have dozens of different clients with a variety of contractual relationships and dynamics of these relationships. Sometimes I have to give the client access to the hosting account or transfer the site to another hosting account.

I have an reseller hosting account and I can create an unlimited number of hosting accounts. It is more convenient for me to have any site in a different hosting account.

This way is more convenient for managing e-mail accounts of clients, for making backups separately for each individual site. In addition I sell hosting services to customers and I provide different volumes hosting space according to the needs of each site.

It's happened to have a hacked site. And it is better to have such an attack affect only one site, not all that I support.

drop's picture

To keep things simple, I would start by creating a Git repository that contains the latest version of Backdrop core, plus the latest version of each contrib module, and/or themes and and layouts) you usually add, plus a copy of your latest configuration files in the `staging` directory.

When you are ready to create new site, clone this repo, install backdrop, enable the modules, then do a config sync (to copy the config from `staging` to `active` and create all necessary database structures).

For a more advanced solution, an install profile could automate the above process -- it would add the modules, enable them, and could probably sync the config for you too.

Most of the process of creating an install profile is unchanged from how it was done in Drupal 7, so I would start with the Drupal 7 documentation for creating an install profile.