2013-07-01 06:54:21 +02:00
|
|
|
## Wordpress+Nginx+PHP-FPM Deployment
|
|
|
|
|
|
|
|
|
|
- Requires Ansible 1.2 or newer
|
|
|
|
|
- Expects CentOS/RHEL 6.x hosts
|
|
|
|
|
|
|
|
|
|
These playbooks deploy a simple all-in-one configuration of the popular
|
|
|
|
|
Wordpress blogging platform and CMS, frontend by the Nginx web server and the
|
2013-10-22 00:10:20 +02:00
|
|
|
PHP-FPM process manager. To use, copy the `hosts.example` file to `hosts` and
|
2013-10-22 00:07:38 +02:00
|
|
|
edit the `hosts` inventory file to include the names or URLs of the servers
|
|
|
|
|
you want to deploy.
|
2013-07-01 06:54:21 +02:00
|
|
|
|
|
|
|
|
Then run the playbook, like this:
|
|
|
|
|
|
|
|
|
|
ansible-playbook -i hosts site.yml
|
|
|
|
|
|
|
|
|
|
The playbooks will configure MySQL, Wordpress, Nginx, and PHP-FPM. When the run
|
|
|
|
|
is complete, you can hit access server to begin the Wordpress configuration.
|
|
|
|
|
|
|
|
|
|
### Ideas for Improvement
|
|
|
|
|
|
|
|
|
|
Here are some ideas for ways that these playbooks could be extended:
|
|
|
|
|
|
|
|
|
|
- Parameterize the Wordpress deployment to handle multi-site configurations.
|
|
|
|
|
- Separate the components (PHP-FPM, MySQL, Nginx) onto separate hosts and
|
|
|
|
|
hande the configuration appropriately.
|
|
|
|
|
- Handle Wordpress upgrades automatically.
|
|
|
|
|
|
|
|
|
|
We would love to see contributions and improvements, so please fork this
|
|
|
|
|
repository on GitHub and send us your changes via pull requests.
|
