-
Notifications
You must be signed in to change notification settings - Fork 32
/
appspec.yml
85 lines (84 loc) · 3.24 KB
/
appspec.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
78
79
80
81
82
83
84
85
# This is an appspec.yml template file for use with an EC2/On-Premises deployment in CodeDeploy.
# The lines in this template starting with the hashtag symbol are
# instructional comments and can be safely left in the file or
# ignored.
# For help completing this file, see the "AppSpec File Reference" in the
# "CodeDeploy User Guide" at
# https://docs.aws.amazon.com/codedeploy/latest/userguide/app-spec-ref.html
version: 0.0
os: linux
# During the Install deployment lifecycle event (which occurs between the
# BeforeInstall and AfterInstall events), copy the specified files
# in "source" starting from the root of the revision's file bundle
# to "destination" on the Amazon EC2 instance.
# Specify multiple "source" and "destination" pairs if you want to copy
# from multiple sources or to multiple destinations.
# If you are not copying any files to the Amazon EC2 instance, then remove the
# "files" section altogether. A blank or incomplete "files" section
# may cause associated deployments to fail.
files:
- source: /
destination: /var/www/wcivf/code/
# For deployments to Amazon Linux, Ubuntu Server, or RHEL instances,
# you can specify a "permissions"
# section here that describes special permissions to apply to the files
# in the "files" section as they are being copied over to
# the Amazon EC2 instance.
# For more information, see the documentation.
# If you are deploying to Windows Server instances,
# then remove the
# "permissions" section altogether. A blank or incomplete "permissions"
# section may cause associated deployments to fail.
permissions:
- object: /var/www/wcivf/code/
pattern: "**"
owner: wcivf
group: wcivf
# If you are not running any commands on the Amazon EC2 instance, then remove
# the "hooks" section altogether. A blank or incomplete "hooks" section
# may cause associated deployments to fail.
hooks:
BeforeInstall:
- location: deploy/before_install/initial_setup.sh
timeout: 300
runas: root
# During the AfterInstall deployment lifecycle event, run the commands
# in the script specified in "location".
AfterInstall:
- location: deploy/after_install/install_python_deps.sh
timeout: 300
runas: wcivf
- location: deploy/after_install/write_envfile.py
timeout: 300
runas: wcivf
- location: deploy/after_install/system_files.sh
timeout: 300
runas: root
- location: deploy/after_install/collectstatic.sh
timeout: 300
runas: wcivf
- location: deploy/after_install/compilemessages.sh
timeout: 300
runas: wcivf
- location: deploy/after_install/install_crontab.sh
timeout: 300
runas: root
# During the ApplicationStart deployment lifecycle event, run the commands
# in the script specified in "location".
ApplicationStart:
- location: deploy/start_application.sh
timeout: 1200
runas: root
AfterBlockTraffic:
- location: deploy/files/scripts/remove_db_replication.sh
timeout: 300
runas: wcivf
# During the ValidateService deployment lifecycle event, run the commands
# in the script specified in "location".
ValidateService:
- location: deploy/validate_application.sh
timeout: 300
runas: root
# - location:
# timeout:
# runas: