Application Launcher

When developing with Site Studio, you will create configuration entities that should be managed using Site Studio's Package management system. Please refer to the following sub-sections of this user guide for clarification on how this differs from Drupal's core configuration workflow as well as detailed explanations on how to export and import/deploy your packages.

Protecting Site Studio credentials

You must not store sensitive Site Studio credentials solely in the database. Manage credentials through environment variables in the settings.php file:

// settings.php
$config['cohesion.settings']['api_key'] = getenv('SITE_STUDIO_API_KEY');
$config['cohesion.settings']['agency_key'] = getenv('SITE_STUDIO_AGENCY_KEY');

Site Studio does not automatically inject these environment variables. You must configure them for each environment. For instructions on how to set up these variables, visit Creating custom environment variables.

This approach ensures the following benefits:

Credentials survive deployment configuration synchronizations.
Version control does not include credentials.
Each environment can use its own set of keys.

Warning

If config_ignore does not protect cohesion.settings and you do not override credentials in the settings.php file, a deployment synchronization can delete your Site Studio API keys. This issue causes rebuild failures and potential downtime.

Protecting Site Studio credentials

You must not store sensitive Site Studio credentials solely in the database. Manage credentials through environment variables in the settings.php file:

// settings.php
$config['cohesion.settings']['api_key'] = getenv('SITE_STUDIO_API_KEY');
$config['cohesion.settings']['agency_key'] = getenv('SITE_STUDIO_AGENCY_KEY');

This approach ensures the following benefits:

Credentials survive deployment configuration synchronizations.
Version control does not include credentials.
Each environment can use its own set of keys.

Protecting Site Studio credentials

You must not store sensitive Site Studio credentials solely in the database. Manage credentials through environment variables in the settings.php file:

// settings.php
$config['cohesion.settings']['api_key'] = getenv('SITE_STUDIO_API_KEY');
$config['cohesion.settings']['agency_key'] = getenv('SITE_STUDIO_AGENCY_KEY');

This approach ensures the following benefits:

Credentials survive deployment configuration synchronizations.
Version control does not include credentials.
Each environment can use its own set of keys.

Warning

Protecting Site Studio credentials

Protecting Site Studio credentials

Did not find what you were looking for?

Protecting Site Studio credentials

Did not find what you were looking for?

Configuration management and deployment

Protecting Site Studio credentials

Configuration management and deployment

Protecting Site Studio credentials

Did not find what you were looking for?

Configuration management and deployment

Protecting Site Studio credentials

Did not find what you were looking for?