forked from acquia/blt
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathproject.yml
77 lines (70 loc) · 2.92 KB
/
project.yml
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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
project:
# Everyone: This will determine the the directory name of the new repository.
# Dev Desktop users: this should match your local site name.
machine_name: 'blted8'
# Used for enforcing correct git commit msg syntax.
prefix: 'BLT'
human_name: 'BLTed 8'
profile:
# You can generate a custom profile by running '../vendor/bin/drupal generate:profile' from the docroot.
name: 'lightning'
# This will be used as the local uri for all developers.
local:
protocol: http
hostname: ${project.machine_name}.localhost
# Configuration settings for new git repository.
git:
default_branch: master
remotes:
# Defining git remotes allows builds deployed via CI.
- [email protected]:bolt8.git
# - [email protected]:radass4.git
commit_message:
regex: '^$BLT-[0-9]+(: )[^ ].{15,}\.'
instructions: |
Invalid commit message. Commit messages must:
* Contain the project prefix followed by a hyphen
* Contain a ticket number followed by a colon and a space
* Be at least 15 characters long and end with a period.
Valid example: BLT-135: Added the new picture field to the article feature.
drush:
# You can set custom project aliases in drush/site-aliases/aliases.drushrc.php.
aliases:
# The remote environment from which the database will be pulled.
remote: ${project.machine_name}.test
# The local environment against which all local drush commands are run.
local: self
# The drush alias against which all ci commands are run.
ci: self
# The default drush alias to be used when no environment is specified.
default_alias: ${drush.aliases.local}
# Custom tasks that are triggered at pre-defined times in the build process.
# The tasks hook into BLT's existing Phing targets. Available hooks keys are:
# frontend-build, post-deploy-build, and post-setup-build.
target-hooks:
# Executed when front end dependencies should be installed.
frontend-setup:
# E.g., ${docroot}/sites/all/themes/custom/mytheme.
dir: ${docroot}
# E.g., `npm install` or `bower install`.
command: echo 'No frontend setup configured.'
# Executed when front end assets should be generated.
frontend-build:
# E.g., ${docroot}/sites/all/themes/custom/mytheme.
dir: ${docroot}
# E.g., `npm run build`.
command: echo 'No frontend build configured.'
# Executed after deployment artifact is created.
post-deploy-build:
dir: ${deploy.dir}/docroot/profiles/contrib/lightning
command: npm run install-libraries
# Executed after setup:build is run.
post-setup-build:
dir: ${docroot}/profiles/contrib/lightning
command: npm run install-libraries
# Define any custom Phing files that you'd like to import. E.g., ${repo.root}/blt/phing/build.xml
import: ~
# Hosting environment flags.
# Examples: acsf (Acquia Cloud Site Factory), ac (Acquia Cloud)
# hosting: "acsf"
# hosting: "ac"