https://github.com/equalitie/open-corroborator-deploy
Issues relating to deploying Corroborator rather than the code itself.
https://github.com/equalitie/open-corroborator-deploy
Last synced: 4 months ago
JSON representation
Issues relating to deploying Corroborator rather than the code itself.
- Host: GitHub
- URL: https://github.com/equalitie/open-corroborator-deploy
- Owner: equalitie
- Created: 2016-02-19T12:54:15.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-04-22T14:23:37.000Z (about 9 years ago)
- Last Synced: 2025-01-04T01:36:42.976Z (5 months ago)
- Size: 37.1 KB
- Stars: 1
- Watchers: 4
- Forks: 0
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# open-corroborator-deploy
Deployment routines for Corroborator.
## Installation
Install Ansible:
```
sudo apt-get install ansible
```
To test deployment on local virtual machines, install Vagrant from https://www.vagrantup.com/downloads.html
## VM install
To create a local virtual machine (VM) and install the software stack onto it:
```
vagrant up
```
This uses Vagrant to create the VM and then Vagrant uses Ansible to install the stack with an environment of 'vm' which uses the ansible `group_vars/vm` settings and the Django `corroborator/settings/vm.py` configuration.
To test the VM, visit http://10.33.33.4/ and login as 'admin' with a password of 'password'.
To re-deploy to the running VM:
```
vagrant provision
```
or
```
ansible-playbook -i ansible/vm ansible/site.yml
```
To stop the local VM:
```
vagrant halt
```
To destroy the local VM:
```
vagrant destroy server1
```
## Create another installation
To use Ansible to install the stack to another target/environment, e.g. _ENV_:
### Create deployment files
In this corroborator-deploy project:
* create an Ansible inventory file, ENV, to give the target machine location - **make sure** the prefix to the `:children` entry is updated to ENV:
```
[ENV:children]
webservers
```
* create an Ansible groups_vars/ENV directory and main.yml file to give the server name, git branch, database password, etc.
### Create settings file
In the open-corroborator project:
* create a Django settings file, corroborator/settings/ENV.py, to give the media locations, initial (non-secret) database password, etc.
By default, uploaded media files are stored and served from the local disk. To store them in Amazon S3, set `QUEUED_STORAGE=True` in the Django settings file and set the `AWS_ACCESS_KEY_ID` and `AWS_STORAGE_BUCKET_NAME`).
If PROD_BUILD is set to True (to use a prebuilt javascript file), you should also set the Ansible variable `run_grunt: yes` (to make sure the file is rebuilt on the server)
## Deploy
Put the SSL certificate files (or links to them) in the following locations (not necessary for the VM deployment):
* /etc/ssl/private/corroborator.key
* /etc/ssl/certs/corroborator.pem
* /etc/ssl/certs/corroborator-intermediates.pem
Then use Ansible to deploy everything:
```
cd ansible
ansible-playbook -i ENV site.yml -K
```
Then make secure by setting the secret settings: login to the target machine and:
a. manually change the secret database password settings, SECRET__KEY, etc. in `/var/local/sites/corroborator/lib/python2.7/site-packages/corroborator/settings/ENV.py`
(including `AWS_SECRET_ACCESS_KEY` if S3 queued storage is being used)
b. change the mysql database password to suit
c. restart the services:
```
sudo service corroborator-gunicorn restart
sudo service corroborator-celery restart
```
d. change the default 'demo' and 'admin' user passwords (see below)
To test, visit the ENV server in a browser and login as 'demo' with a password of 'demo'.
The 'admin' user password is intially set to 'password'.