The base application on Acquia Cloud hosting the Sitenow platform.

This project is based on BLT, an open-source project template and tool that enables building, testing, and deploying Drupal installations following Acquia Professional Services best practices. While this is one of many methodologies, it is our recommended methodology.

1. Review the Required / Recommended Skills for working with a BLT project.
2. Ensure that your computer meets the minimum installation requirements (and then install the required applications). See the System Requirements.
3. Request access to organization that owns the project repo in GitHub (if needed).
4. Request access to the Acquia Cloud Environment for your project (if needed).
5. Setup a SSH key that can be used for GitHub and the Acquia Cloud (you CAN use the same key).
   1. Setup GitHub SSH Keys
   2. Setup Acquia Cloud SSH Keys
6. Clone the repository. By default, Git names this "origin" on your local.

   $ git clone [email protected]:<account>/[email protected]/uiowa/uiowa.git
   

7. Update your the configuration located in the /blt/blt.yml file to match your site's needs. See configuration files for other important configuration files.

1. Install Drush Launcher.
   • Ensure that there are no other Drush versions in your $PATH in ~/.bashrc or ~.bash_profile.
2. Install Homebrew.
3. Install PHP 7.2 via Homebrew.

   brew install [email protected]
   brew link [email protected]
   

   Follow the instructions to get PHP7.2 in your $PATH.
4. Install MariaDB.

   brew install mariadb
   

   Keep the username root with no password.
5. Start MariaDB.

   brew services start mariadb
   

6. Install Composer dependencies.

   $ composer install
   

7. Sync all multisites.

   blt drupal:sync:all-sites
   

   or blt dsa for short.
8. Start the built-in PHP server.

   $ drush -l mysite rs --dns
   

Visit the site in your browser by navigating to http://localhost:8888. You can log in using drush -l mysite uli, although Drush returns the incorrect URI. Copy the path and append to http://localhost:8888.

The drush/Commands/PolicyCommands.php file will overwrite the sites.local.php file to route the correct site when running drush rs. It is possible to serve multiple sites from different runserver commands with two different ports. You'll need to manually edit the sites.local.php file in that scenario.

The drupal:sync:all-sites command will generate settings files only if they do not exist. If you want to re-generate all multisite local settings files, you can run rm -f docroot/sites/*/settings/local.settings.php beforehand.

Additional BLT documentation may be useful. You may also access a list of BLT commands by running this:

$ blt

BLT projects are designed to instill software development best practices (including git workflows).

Our BLT Developer documentation includes an example workflow.

BLT uses a number of configuration (.yml or .json) files to define and customize behaviors. Some examples of these are:

• blt/blt.yml (formerly blt/project.yml prior to BLT 9.x)
• blt/local.blt.yml (local only specific blt configuration)
• box/config.yml (if using Drupal VM)
• drush/sites (contains Drush aliases for this project)
• composer.json (includes required components, including Drupal Modules, for this project)

• GitHub - https://github.com/uiowa/uiowa
• Acquia Cloud subscription - https://cloud.acquia.com/app/develop/applications/6bcc006f-9a0e-425e-aba0-198585dd2b56