|
1 | 1 | ---
|
2 |
| -remote_tmp: "" |
3 |
| -ansible_connection: "ssh" |
4 |
| -backup_directory: "{{ remote_tmp }}/unfetter" |
5 |
| -ansible_user: "ansible" |
6 |
| -ansible_ssh_private_key_file: "xxxxxxx" |
| 2 | + |
| 3 | +###################################################################################################### |
| 4 | + |
| 5 | +# This file is a demonstration of the variables you may need to override in order to customize |
| 6 | +# Unfetter deployment to meet your needs. |
| 7 | + |
| 8 | +# Each file in the host_vars directory should be named after your deployment type |
| 9 | +# - prod-uac.yml |
| 10 | +# - prod-legacy-demo.yml |
| 11 | +# - prod-legacy-uac.yml |
| 12 | +# - prod-demo.yml |
| 13 | + |
| 14 | +# For developers, a 'build.yml' may also be necessary. |
| 15 | + |
| 16 | +# Every variable in a hosts file will override all group vars. Consider the group_vars files to be default values |
| 17 | + |
| 18 | +###################################################################################################### |
| 19 | + |
| 20 | + |
| 21 | + |
| 22 | + |
| 23 | +###################################################################################### |
| 24 | +# Connection Variables |
| 25 | +# These variables are needed to connect to your system that is running Unfetter. By default, |
| 26 | +# the group_vars will set the variables to support a local deployment. Meaning, that ansible is |
| 27 | +# executed on the same system that you will run Unfetter. |
| 28 | + |
| 29 | +# For a local system, the values will be |
| 30 | + |
| 31 | +# ansible_connection: "local" |
| 32 | +# ansible_user: "" |
| 33 | +# ansible_ssh_private_key_file: "" |
| 34 | +# ansible_host: "127.0.0.1" |
| 35 | +# backup_directory: "{{ playbook_dir }}/backup" |
| 36 | + |
| 37 | +# For remote system accessed over SSH, which is where Ansible excels, you would change those values to the following: |
| 38 | +###################################################################################### |
| 39 | + |
| 40 | +# Tell Ansible host how to connect with the host. ssh |
| 41 | +ansible_connection: "ssh" |
| 42 | + |
| 43 | +# The user that the host running ansible will connect to the remote system. You are responsible |
| 44 | +# for creating this user. For AWS, it is likely ec2-user |
| 45 | +ansible_user: "ec2-user" |
| 46 | + |
| 47 | +# The private key file and location |
| 48 | +ansible_ssh_private_key_file: "~/.ssh/id_rsa" |
| 49 | + |
| 50 | +# What is the host IP that you will SSH into. |
7 | 51 | ansible_host: "xx.xx.xxx.xxx"
|
8 |
| -api_domain: "{{ ansible_host }}" |
9 |
| -ui_domain: "{{ ansible_host }}" |
10 | 52 |
|
| 53 | +# The backup directory is where backup files are stored, and where Unfetter will look for the files to restore |
| 54 | +# data from. For remote deployments, there is no ansible directory so {{ playbook_dir }} has to be overwritten |
| 55 | +backup_directory: "/tmp/backup" |
| 56 | + |
| 57 | +###################################################################################### |
| 58 | +# In UAC deployed, these values are needed as the domain that people are accessing Unfetter. If you are running |
| 59 | +# locally, as the default setting, this is localhost. For a real deployment, it is the domain name or IP address |
| 60 | + |
| 61 | +api_domain: "www.example.com" |
| 62 | +ui_domain: "www.example.com" |
| 63 | + |
| 64 | + |
| 65 | +###################################################################################### |
11 | 66 | # If you are using a proxy URL, you can change that here, otherwise, leave it commented out
|
| 67 | +###################################################################################### |
| 68 | + |
| 69 | + |
12 | 70 | # https_proxy_url: "http://host:port"
|
0 commit comments