-
Notifications
You must be signed in to change notification settings - Fork 5
/
appspec.yml
104 lines (103 loc) · 3.81 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
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
# This is an appspec.yml template file for use with an EC2/On-Premises deployment in AWS CodeDeploy.
version: 0.0
os: linux
# Specify multiple "source" and "destination" pairs if you want to copy
# from multiple sources or to multiple destinations.
files:
- source: vision/
destination: /home/ec2-user/BSI_CodeDeploy/src/vision/
- source: bsi_shared/
destination: /home/ec2-user/BSI_CodeDeploy/src/bsi_shared/
# 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.
permissions:
- object: vision/
owner: ec2-user
type:
- directory
- object: bsi_shared/
owner: ec2-user
type:
- directory
# group:
# mode:
# acls:
# -
# context:
# user:
# type:
# range:
# 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:
# For each deployment lifecycle event, specify multiple "location" entries
# if you want to run multiple scripts during that event.
# You can specify "timeout" as the number of seconds to wait until failing the deployment
# if the specified scripts do not run within the specified time limit for the
# specified event. For example, 900 seconds is 15 minutes. If not specified,
# the default is 1800 seconds (30 minutes).
# Note that the maximum amount of time that all scripts must finish executing
# for each individual deployment lifecycle event is 3600 seconds (1 hour).
# Otherwise, the deployment will stop and AWS CodeDeploy will consider the deployment
# to have failed to the Amazon EC2 instance. Make sure that the total number of seconds
# that are specified in "timeout" for all scripts in each individual deployment
# lifecycle event does not exceed a combined 3600 seconds (1 hour).
# For deployments to Amazon Linux, Ubuntu Server, or RHEL instances,
# you can specify "runas" in an event to
# run as the specified user. For more information, see the documentation.
# If you are deploying to Windows Server instances,
# remove "runas" altogether.
# If you do not want to run any commands during a particular deployment
# lifecycle event, remove that event declaration altogether. Blank or
# incomplete event declarations may cause associated deployments to fail.
# During the ApplicationStop deployment lifecycle event, run the commands
# in the script specified in "location" starting from the root of the
# revision's file bundle.
# ApplicationStop:
# - location:
# timeout:
# runas:
# - location:
# timeout:
# runas:
# During the BeforeInstall deployment lifecycle event, run the commands
# in the script specified in "location".
# BeforeInstall:
# - location:
# timeout:
# runas:
# - location:
# timeout:
# runas:
# During the AfterInstall deployment lifecycle event, run the commands
# in the script specified in "location".
# AfterInstall:
# - location:
# timeout:
# runas:
# - location:
# timeout:
# runas:
# During the ApplicationStart deployment lifecycle event, run the commands
# in the script specified in "location".
# ApplicationStart:
# - location:
# timeout:
# runas:
# - location:
# timeout:
# runas:
# During the ValidateService deployment lifecycle event, run the commands
# in the script specified in "location".
# ValidateService:
# - location:
# timeout:
# runas:
# - location:
# timeout:
# runas: