https://github.com/tinuva/opsworks-wordpress-app
Wordpress - Ready to be used as application on AWS OpsWorks
https://github.com/tinuva/opsworks-wordpress-app
Last synced: 2 months ago
JSON representation
Wordpress - Ready to be used as application on AWS OpsWorks
- Host: GitHub
- URL: https://github.com/tinuva/opsworks-wordpress-app
- Owner: tinuva
- License: other
- Created: 2017-04-25T09:23:40.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2017-04-29T08:31:28.000Z (about 8 years ago)
- Last Synced: 2025-01-17T20:24:36.121Z (4 months ago)
- Language: PHP
- Size: 16.5 MB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: license.txt
Awesome Lists containing this project
README
# opsworks-wordpress-app
Wordpress - Ready to be used as application on AWS OpsWorks
## Getting started
1. Launch a new OpsWorks **Chef 11 Stack** from [here](https://console.aws.amazon.com/opsworks/home?owc=true)
2. Add **MySQL Layer**, then add one instance to the MySQL layer and start it
* Optional, instead of a MySQL layer you can add a RDS layer
NB. When creating the RDS instance, also create a database to be used with OW
3. Add **PHP App Server** layer, add an instance to the layer and start it
4. Add a new App
* App Name: wordpress
* Data source type is OpsWorks, unless in step 2 RDS is used
* If RDS was used in step 2, use database name created in step 2
* Application source:
* Repository Type = git
* Repository URL = https://github.com/tinuva/opsworks-wordpress-app.git
5. Wait for all instances to be in 'running' state
6. Deploy App to all instances
7. At this point, the Wordpress install is finished. Visit the IP address of your instance and set up your wordpress install.
## What to do next
1. Add more instances to the PHP layer
2. Create a Classic ELB
* On a note, the health check should be on '/' instead of the default '/index.html'
3. Edit the PHP App Server layer, then attach the ELB created in previous step