This repository contains the Ansible Playbooks we use to configure our Website Server & to deploy the lastest Website Code.
You need ansible installed to run this playbook. The ansible.cfg in this
repository will attempt to SSH into the server as your current user and will
prompt for your sudo password.
Sensitive playbook-variables are stored in the group_vars/all/vault file. You
can edit this file with our vault password by running ansible-vault edit group_vars/all/vault. For convenience, you can put the vault password in a
vault-password file in this folder to prevent ansible from prompting you for
the password. A .gitignore rule will prevent checking the password file into
the repository.
To run a playbook, simple run ansible-playbook <playbook-name>.yaml. By
default, the playbooks will run against a local VM that is expected to have a
DNS name of sese-www-test.acorn. Before running the playbook, you should
ensure that the VM is running and your computer will resolve the domain name
to it. You can edit your /etc/hosts file to point the domain to your VMs IP
if you do not have access to a DNS server, or edit the hosts.yaml file to
point to the proper domain or IP address.
To run a playbook against our staging or production hosts, you must pass
the host or group name to the ansible-playbook command via the host
variable:
ansible-playbook --extra-vars "host=staging" playbook-configure.yamlplaybook-configure.yaml is the playbook responsible for configuring a server.
The playbook will:
- Install basic sysadmin tools
- Setup user accounts for administrators
- Configure MSMTP for sending emails
- Enable unattended package upgrades for security updates
- Harden the SSH server
- Configure the ufw firewall
- Install nginx & configure it to proxy the API server and serve the static files
- Install & configure certbot for generating nginx's SSL certificates
- Install PostgreSQL, setup the database for the API server, & tune the configuration for performance
- Install Stack & NodeJS, create a user for the website, clone & build the website code, deploy the static files, and configure & install a systemd service for the API server
- Setup a local Prerender instance with systemd to handle server side rendering for web crawlers and bots
playbook-deploy.yaml is the playbook responsible for deploying the lastest
master branch of our repository to a server. It assumes that the
configuration playbook has already been run on the server at least once.
The deployment playbook will:
- Reset the repository on the server.
- Pull the latest code.
- Ensure the local copy has the
masterbranch checked out. - Make a production build of the client & server.
- Install the API server & client files.
- Restart the API server & prerender server.
GPL-3.0