Skip to content

Latest commit

 

History

History
82 lines (48 loc) · 4.45 KB

onboarding.md

File metadata and controls

82 lines (48 loc) · 4.45 KB

Onboarding

Here is a quick-start guide to getting your local development environment set up and getting oriented with the project standards and workflows.

Required SAAS Access:

Please ask the project's engagement manager for access to the following SaaS services:

  • JIRA
  • GitHub repository
  • Acquia Cloud subscription

System Requirements

Verify that your system meets System requirements

Networking considerations

Building project dependencies requires that your local machine make HTTP and HTTPS requests to various software providers on the internet. Please ensure that your local and network level security settings permit this to happen.

If you need to make requests via a proxy server, please configure git to use a proxy. This will cover all git based requests made by Composer.

Initial Setup

  1. Fork the primary GitHub repository

  2. Clone your fork to your local machine:

      git clone [email protected]:username/project-repo.git
  git remote add upstream [email protected]:acquia-pso/project-repo.git

  3. If your project uses separate master and develop branches, checkout the develop branch: git checkout develop

  4. Run composer install (you must already have Composer installed).

  5. Install blt alias: composer blt-alias

If your project uses a virtual development environment such as DrupalVM:

  1. Make sure you have installed any prerequisites. For DrupalVM, see the quick start guide.
  2. Start your virtual machine: blt vm
  3. Build and install the Drupal installation: blt local:setup

If your project does not use a virtual development environment:

  1. Setup your local LAMP stack with the webroot pointing at you project's docroot directory.
  2. Run blt setup:settings This will generate docroot/sites/default/settings/local.settings.php and docroot/sites/default/local.drushrc.php. Update these with your local database credentials and your local site URL.
  3. Run blt local:setup. This will build all project dependencies and install drupal.
  4. Create and edit your local drush alias file. Copy drush/site-aliases/example.local.aliases.drushrc.php to drush/site-aliases/local.aliases.drushrc.php. Edit the new alias file with your local path.

Please see Local Development for more information on setting up a local *AMP stack or virtual development environment.

Ongoing development

As development progresses, you can use the following commands to keep your local environment up to date:

  • Run blt local:setup to rebuild the codebase and reinstall your Drupal site (most commonly used early in development).
  • Run blt local:refresh to rebuild the codebase, import a fresh DB from a remote environment, and run schema/configuration updates (most commonly used later in development).

Each of these commands is simply a wrapper for a number of more granular commands that can be run individually if desired (for instance, blt local:update just runs database updates and imports configuration changes). For a full list of available project tasks, run blt -l. See Project Tasks for more information.

Local Git Configuration

For readability of commit history, set your name and email address properly:

git config user.name "Your Name"
git config user.email [email protected]

Ensure that your local email address correctly matches the email address for your Jira account.

Updating you local environment

The project is configured to update the local environment with a local drush alias and a remote alias as defined in project.yml or project.local.yml. Given that these aliases match, those in drush/site-aliases/, you can update the site with BLT.

Local Development Tasks

GitHub Configuration

In order to more easily identify developers in a project, please be sure to set a name and profile picture in your GitHub profile.

When working with GitHub, the hub utility can be helpful when managing forks and pull requests. Installing hub largely depends on your local environment, so please follow the installation instructions accordingly.

Next steps

Review BLT documentation by role to learn how to perform common project tasks and integrate with third party tools.