Skip to content

VibrentHealth

For drupalStand documentation visit drupalStand README.

Dev QA env https://mtwplatform-qa.qak8s.vibrenthealth.com/

Dev env http://mtwplatform.qak8s.vibrenthealth.com/

Jira Story Points reference

Time off schedule

Requirements

Tools

Lando (Drush and Composer)

  • Req. Lando version: > 3.0 ?
  • Lando config (.lando.yml) and .env files will be committed to repo soon, in the meantime, you can use this config as example:
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
name: vibrent-demo
recipe: drupal8
config:
  webroot: webroot
  php: '7.2'
  via: nginx
  drush: composer
  xdebug: true
  conf:
    php: php.ini
services:
  database:
    type: mariadb:10.1
  mailhog:
    type: mailhog
    hogfrom:
      - appserver
  appserver:
    overrides:
      environment:
        # Support debugging Drush with XDEBUG.
        PHP_IDE_CONFIG: "serverName=appserver"
  node:
    type: node
    globals:
      gulp-cli: "latest"
      node-sass: "latest"
    build:
      - "cd $LANDO_MOUNT/webroot/themes/custom/vibrent && npm install && npm install node-sass"
      - gulp
proxy:
  appserver:
    - dev.vibrent.com
  mailhog:
    - mail.vibrentdemo.lndo.site
tooling:
  npm:
    service: node
  node:
    service: node
  gulp:
    service: node
  yarn:
    service: node

1
2
3
4
5
6
MYSQL_USER=drupal8
DRUPAL_MYSQL_HOST=database
MYSQL_PASSWORD=drupal8
MYSQL_DATABASE=drupal8
PHP_IDE_CONFIG="serverName=appserver"
xdebug.extended_info=1

Git

In order to be able to push/pull from the VH repository you need to be added as a member. Please remember to add your Vibrent email (usually something like name@vibrenthealth.com) tou your github profile.

If you were creating PR’s against dev branch in Mobomo repository, you will need to add a new remote to be able to push your code agains VH repo:

1
git remote add vhmtwplatform git@github.com:VibrentHealth/mtwplatform.git
Where vhmtwplatform is the name for the new remote. So you could push code using something like:

1
git push vhmtwplatform yourname/MTW-123_branch_name

Guide for commiting new code

First of all: Always make sure to pull dev branch (or the base branch you are going to commit your PR in VH repo this would be develop in most cases for new code) before starting your work. This will most probably avoid you merge conflicts later on.

Set your local env to be up-to-date with upstream

1
2
3
git pull
lando composer install
lando drush cim

(docs to be continued…)

NOTES

Commands run in site-install / config import process (check with Clinton / scripts)

1
lando drush site-install minimal -vvv --yes --account-name=admin --account-pass=SomethinglongAndmemorable5! --account-mail=dp_admin@mobomo.com install_configure_form.enable_update_status_module=NULL install_configure_form.enable_update_status_emails=NULL

1
cat config/system.site.yml | grep uuid | tail -c +7 | head -c 36 | lando drush config-set -y system.site uuid -