forked from p-blomberg/Web-app-deploy-script
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdeploy_settings_example.sh
More file actions
36 lines (26 loc) · 933 Bytes
/
deploy_settings_example.sh
File metadata and controls
36 lines (26 loc) · 933 Bytes
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
#!/path/to/deploy.sh
# Repository type (git or svn)
VCS="git"
# All relative paths are relative to the directory this configuration exists in.
# A lock file is used to ensure multiple deploys aren't run at the same time.
# LOCK_FILE=deploy.lock
# Path to an existing working copy (user must checkout/clone the repository
# before the first deploy, the deploy script only updates/pulls new revisions)
RELEASE_WC=working_copy
# Directory where exported versions will be placed
EXPORT_TARGET=/var/www/site/releases
# Symlink target for the latest release
SYMLINK_PATH=/var/www/site/example.com
# How many old releases to retain.
# RELEASE_COUNT=8
# File patterns to remove from the export. If you create a custom
# `export_post_hook` you must manually call `file_prune` if you need this
# feature.
# PRUNE=(o
# ".*\.xcf"
# )
# Sample hook
# update_post_hook(){
# echo "in overloaded post update hook"
# }
SETTINGS_FILE_OK=1