ZohoCRM Confirguration

  • Home
  • ZohoCRM Confirguration

ZohoCRM Configuration Management

configuration is the collection of admin settings that determine how the site functions, as opposed to the content of the site. Configuration will typically include things such as the site name, the content types and fields, taxonomy vocabularies, views and so on.

Managing your site's configuration

Changing the storage location of the sync directory

Development modules excluded from configuration

Keeping Your Local and Remote Sites Synchronized

Workflow using Drush

File system based workflow

Managing your site's configuration

Making configuration changes on a live site is not recommended. The system is designed to make it easy to take the live configuration, test changes locally, export them to files, and deploy to production. Your site’s configuration can be stored as part of your codebase and integrated with version control.

Exporting and importing configuration changes between a Drupal installation in different environments, such as Development, Staging, and Production, allows you to make and verify your changes with a comfortable distance from your site’s live environment.

This allows you to deploy a configuration from one environment to another (as a precaution, Drupal checks the site is the same before importing, by comparing its UUID).

Changing the storage location of the sync directory

On production sites, and if your account has permission to do so, it’s a good idea to move the configuration sync directory outside of the webroot entirely. As your sync directory should be under version control, this means having your version control repository’s root be one level higher than your webroot.

 The HASH is a pretty long string of random characters. This makes configuration more difficult (but not impossible) to be accessed over the web. The sync directory location can be changed after installation.


Development modules excluded from configuration management

Some modules are enabled by developers on their local instance of their drupal site but are not meant to be enabled on the production site.

The manual solution to this is to un-install the module before doing a configuration export and to manually install it again locally after a configuration import.