During normal Drupal development, when you’re developing your website’s themes, best practices would have you store a theme’s files in the sites/all/themes directory under your docroot directory. If you want a design team to create and maintain your websites’ theme files without granting them access to your websites’ code, you can set up an external theme repository.
Site Factory allows you to configure a link to an external Git repository containing one or more themes for use with your Drupal website. After connecting your website to a Git repository containing one or more themes, the themes will display when you click Appearance in the admin menu.
Git repository requirements
When creating your external Git repository, ensure the repository contains the following items:
One or more branches or tags.
One or more sets of Drupal theme files to use with your website. Place each theme’s file in a separate directory, named with the theme’s name.
Cloud Platform requires deployment keys be associated with a user account. As GitHub does not support the use of the same deployment key for multiple repositories, create a Cloud Platform user as described in Deployment keys and Cloud Platform. Associate the key with a user account, instead of adding the SSH key as a deployment key.
Creating a theme repository allowlist
To protect hosted websites from using themes containing potentially harmful settings or code, you can add a allowlist file of approved theme repositories to Site Factory. When administrative users try to add a theme repository, Site Factory compares the repository with the contents of the acsf_theme_allowlist.txt file.
To create an allowlist file for your theme repositories:
Create a file to contain your allowlist settings, based on the following conventions:
Enter each external Git repository on a separate line.
You can add comments to entries by starting lines with the number sign ( # ). The # isn’t used for allowlist filtering.
Use the asterisk character ( * ) for wildcard entry.
If you don’t end a repository line with an asterisk, its use is implied.
Save the file with the name acsf_theme_allowlist.txt in the root directory of your code repository.
Commit your code changes with the new allowlist file to your codebase.
Deploy the code to your production environment.
Example
The following allowlist file allows only theme repositories from the Acquia organization on github.com, the Open Framework repository on github.com, and the zen.git repository on drupal.org:
# Allow any github repos from the Acquia organization
github.com:acquia/*
# Allow specific github repo
github.com:SU-SWS/open_framework
# Allow the Zen theme from Drupal.org
git.drupal.org:project/zen.git
If you don’t upload a allowlist file, or if the file does not contain any entries, Site Factory will not block any theme repositories from use.
Connecting to a theme repository
To connect to an external Git repository containing one or more themes:
Find the website you want to modify, open its actions menu, and then click Manage theme repository.
Click Connect site repository to enter your Git repository’s information.
Click the Show SSH public key link to display the SSH public key.
Select and copy the contents of the SSH public key field to your clipboard.
Open a new browser tab and sign in to your Git repository.
Add the SSH public key to the theme repository, and configure the key to have read access.
Open a new browser tab and sign in to the Acquia user account.
Add the SSH public key to the user account.
Return to the page in which you are entering your theme repository information, and then enter the following values for the Git repository you want to use:
Git URL: The Git SSH URL of the theme repository (for example, [email protected]:repo.git)
Branch or tag: A valid branch or tag from the theme repository
Site Factory compares theme repositories to entries in the allowlist file based on the following parameters:
The user@ preceding the theme repository is ignored.
Theme repositories beginning with an exact match of one or more of the allowlist file entries are accepted. For example, a allowlist entry of github.com would match [email protected]:repo.git.
If the allowlist file blocks a theme repository, Site Factory will display an error message and keep the previous theme repository settings.
If no error messages display, your Git repository themes will be checked out for use by your website. After the checkout completes, you can view the themes by signing in to the website and clicking Appearance in the admin menu.
Note
There may be a delay between associating your Git theme repository with your website and the availability of its themes on the Appearance page. For example, delays can be more noticeable during updates or staging processes.
Refreshing your theme
Whenever you make changes to your theme files, and commit those changes to the Git theme repository, you must update your websites’ theme files based on the correct branch or tag. You must update every website using the updated theme.
Find the website you want to modify, open its actions menu, and then click Manage theme repository.
Select the appropriate method based on whether you are using a branch (staged websites) or a tag (production websites):
Branch: Click Refresh themes.
Tag –
Click the Change site theme repository link.
In the Branch or tag list, click the tag with the new theme changes.
Site Factory obtains your new theme changes from the Git repository and adds them to your website. After it makes copies of the theme files, the theme changes display in the website’s Appearance page (and if the theme is in use, on the website itself).
Note
You may see a delay between associating your Git theme repository with your website, and the availability of its themes on the Appearance page. For example, delays can be more noticeable during updates or staging processes.
Performing custom actions after theme deployments
You can use the post-theme-deploy Factory hook to clear Twig caches or perform other actions after deploying a theme. The post-theme-deploy Factory hook makes a set of arguments available to any script executed by the hook:
Domain: Represents (Acquia managed) domain name of the website. For example, in the URL mysite.demo.acsitefactory.com, the first part mysite represents the name that’s unique for each installed website.
Note
If you delete a website and recreate it with the same name, it get’s a different database role (unique identifier).
Using these arguments, you can create a script like the following example, which runs a Drush command to clear the Twig cache on the affected site on every server. Site Factory supplies the needed host, environment, and domain values:
#!/bin/bash
drush8 @$1.$2 --uri=$5 ev '\Drupal\Core\PhpStorage\PhpStorageFactory::get("twig")->deleteAll();'
Create a script file with a name like ClearTwigCache, with content similar to the previous example. The script must be executable, as described in Executing your commands with a hook.
Save and commit the script file in your code repository in the /factory-hooks/post-theme-deploy directory.
During normal Drupal development, when you’re developing your website’s themes, best practices would have you store a theme’s files in the sites/all/themes directory under your docroot directory. If you want a design team to create and maintain your websites’ theme files without granting them access to your websites’ code, you can set up an external theme repository.
Site Factory allows you to configure a link to an external Git repository containing one or more themes for use with your Drupal website. After connecting your website to a Git repository containing one or more themes, the themes will display when you click Appearance in the admin menu.
Git repository requirements
When creating your external Git repository, ensure the repository contains the following items:
One or more branches or tags.
One or more sets of Drupal theme files to use with your website. Place each theme’s file in a separate directory, named with the theme’s name.
Cloud Platform requires deployment keys be associated with a user account. As GitHub does not support the use of the same deployment key for multiple repositories, create a Cloud Platform user as described in Deployment keys and Cloud Platform. Associate the key with a user account, instead of adding the SSH key as a deployment key.
Creating a theme repository allowlist
To protect hosted websites from using themes containing potentially harmful settings or code, you can add a allowlist file of approved theme repositories to Site Factory. When administrative users try to add a theme repository, Site Factory compares the repository with the contents of the acsf_theme_allowlist.txt file.
To create an allowlist file for your theme repositories:
Create a file to contain your allowlist settings, based on the following conventions:
Enter each external Git repository on a separate line.
You can add comments to entries by starting lines with the number sign ( # ). The # isn’t used for allowlist filtering.
Use the asterisk character ( * ) for wildcard entry.
If you don’t end a repository line with an asterisk, its use is implied.
Save the file with the name acsf_theme_allowlist.txt in the root directory of your code repository.
Commit your code changes with the new allowlist file to your codebase.
Deploy the code to your production environment.
Example
The following allowlist file allows only theme repositories from the Acquia organization on github.com, the Open Framework repository on github.com, and the zen.git repository on drupal.org:
# Allow any github repos from the Acquia organization
github.com:acquia/*
# Allow specific github repo
github.com:SU-SWS/open_framework
# Allow the Zen theme from Drupal.org
git.drupal.org:project/zen.git
If you don’t upload a allowlist file, or if the file does not contain any entries, Site Factory will not block any theme repositories from use.
Connecting to a theme repository
To connect to an external Git repository containing one or more themes:
Find the website you want to modify, open its actions menu, and then click Manage theme repository.
Click Connect site repository to enter your Git repository’s information.
Click the Show SSH public key link to display the SSH public key.
Select and copy the contents of the SSH public key field to your clipboard.
Open a new browser tab and sign in to your Git repository.
Add the SSH public key to the theme repository, and configure the key to have read access.
Open a new browser tab and sign in to the Acquia user account.
Add the SSH public key to the user account.
Return to the page in which you are entering your theme repository information, and then enter the following values for the Git repository you want to use:
Git URL: The Git SSH URL of the theme repository (for example, [email protected]:repo.git)
Branch or tag: A valid branch or tag from the theme repository
Site Factory compares theme repositories to entries in the allowlist file based on the following parameters:
The user@ preceding the theme repository is ignored.
Theme repositories beginning with an exact match of one or more of the allowlist file entries are accepted. For example, a allowlist entry of github.com would match [email protected]:repo.git.
If the allowlist file blocks a theme repository, Site Factory will display an error message and keep the previous theme repository settings.
If no error messages display, your Git repository themes will be checked out for use by your website. After the checkout completes, you can view the themes by signing in to the website and clicking Appearance in the admin menu.
Note
There may be a delay between associating your Git theme repository with your website and the availability of its themes on the Appearance page. For example, delays can be more noticeable during updates or staging processes.
Refreshing your theme
Whenever you make changes to your theme files, and commit those changes to the Git theme repository, you must update your websites’ theme files based on the correct branch or tag. You must update every website using the updated theme.
Find the website you want to modify, open its actions menu, and then click Manage theme repository.
Select the appropriate method based on whether you are using a branch (staged websites) or a tag (production websites):
Branch: Click Refresh themes.
Tag –
Click the Change site theme repository link.
In the Branch or tag list, click the tag with the new theme changes.
Site Factory obtains your new theme changes from the Git repository and adds them to your website. After it makes copies of the theme files, the theme changes display in the website’s Appearance page (and if the theme is in use, on the website itself).
Note
You may see a delay between associating your Git theme repository with your website, and the availability of its themes on the Appearance page. For example, delays can be more noticeable during updates or staging processes.
Performing custom actions after theme deployments
You can use the post-theme-deploy Factory hook to clear Twig caches or perform other actions after deploying a theme. The post-theme-deploy Factory hook makes a set of arguments available to any script executed by the hook:
Domain: Represents (Acquia managed) domain name of the website. For example, in the URL mysite.demo.acsitefactory.com, the first part mysite represents the name that’s unique for each installed website.
Note
If you delete a website and recreate it with the same name, it get’s a different database role (unique identifier).
Using these arguments, you can create a script like the following example, which runs a Drush command to clear the Twig cache on the affected site on every server. Site Factory supplies the needed host, environment, and domain values:
#!/bin/bash
drush8 @$1.$2 --uri=$5 ev '\Drupal\Core\PhpStorage\PhpStorageFactory::get("twig")->deleteAll();'
Create a script file with a name like ClearTwigCache, with content similar to the previous example. The script must be executable, as described in Executing your commands with a hook.
Save and commit the script file in your code repository in the /factory-hooks/post-theme-deploy directory.
To ensure that the theme changes for one website do not affect other websites that use the same theme, Acquia recommends you to use discrete tags for all environments. However, it is worth noting that using branches for staged websites can speed your theme development process.
Click Save.
Click Save.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Note
To ensure that the theme changes for one website do not affect other websites that use the same theme, Acquia recommends you to use discrete tags for all environments. However, it is worth noting that using branches for staged websites can speed your theme development process.
Site Factory