Mount SECRET_KEY into dev env & document it

This commit is contained in:
Christian M. Adams 2021-02-22 18:28:08 -05:00
parent b583aeb646
commit ec40f62c4d
No known key found for this signature in database
GPG Key ID: F41796178F693C8E
3 changed files with 9 additions and 0 deletions

View File

@ -30,6 +30,12 @@
when: not lookup('vars', item.item, default='')
loop: "{{ secrets.results }}"
- name: Write out SECRET_KEY
copy:
content: "{{ secret_key }}"
dest: "{{ sources_dest }}/SECRET_KEY"
no_log: true
- name: Render configuration templates
template:
src: "{{ item }}.j2"

View File

@ -30,6 +30,7 @@ services:
- "../../docker-compose/_sources/database.py:/etc/tower/conf.d/database.py"
- "../../docker-compose/_sources/websocket_secret.py:/etc/tower/conf.d/websocket_secret.py"
- "../../docker-compose/_sources/local_settings.py:/etc/tower/conf.d/local_settings.py"
- "../../docker-compose/_sources/SECRET_KEY:/etc/tower/SECRET_KEY"
- "redis_socket:/var/run/redis/:rw"
privileged: true
tty: true

View File

@ -5,6 +5,8 @@ migrate your data to the development environment via the migrate.yml playbook, o
> Note: This will also convert your postgresql bind-mount into a docker volume.
First, in the `inventory` file, set your `pg_password`, `broadcast_websocket_secret`, `secret_key`, and any other settings you need for your deployment. **Make sure you use the same secret key value you had with your previous Local Docker deployment.**
### Migrate data with migrate.yml
If you had a custom pgdocker or awxcompose location, you will need to set the `postgres_data_dir` and `old_docker_compose_dir` variables.