Use Docker to provide a WordPress / Laravel environment which will be easy to use for local development and for deploying to the cloud (AWS)
- Local windows development environment (using Docker)
- Pushing to git ==> will automatically get latest code deployed live in production (without having to manually FTP upload PHP files or anything like that)
- Required project source code pushed to this github repository
- Document with detailed and clear steps how to achieve everything described in the below section called How Testing Will Be Done
- Docker - https://www.docker.com
- Laradock - http://laradock.io
- Dokku - https://github.com/dokku/dokku
- Composer - https://getcomposer.org
- Laravel - https://laravel.com
- WordPress - https://wordpress.org
- Bedrock WordPress project boilerplate - https://github.com/roots/bedrock
- Sage9 WordPress starter theme - https://github.com/roots/sage
- Adminer - https://www.adminer.org
- The AWS Elastic Beanstalk Command Line Interface (EB CLI) - https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3.html ( or AWS command line tools or AWS ECS command line tools - whichever is more appropriate)
https://apps.domain.com (WordPress should be available here - with the Sage 9 starter theme)
https://apps.domain.com/wp-admin (WordPress admin should be available here)
https://apps.domain.com/lara-admin (Laravel starter app should be available here)
- Delete everything related with the wordpress-laravel-docker-local-cloud project from local computer (Windows)
- git clone the wordpress-laravel-docker-local-cloud project repository from github
Without any further / manual configuration WordPress, Laravel (/lara-admin) and Adminer should work fine when started both locally and in the AWS cloud (WordPress and Adminer should not require any additional installation everything should be correctly pre-installed and configured inside the docker containers). Adminer should be pre-configured to connect to the WordPress MySQL database.
Laravel - Change the default "hello word" lara-admin entry point and refresh the browser's locally corresponding https://apps.company.com/lara-admin/ URL and then make sure the changed Laravel starter hello world version is coming
WordPress - Modify Sage9's index.blade.php https://github.com/roots/sage/blob/master/resources/views/index.blade.php refresh the browser's locally corresponding https://apps.company.com URL and make sure the update version is coming
No manual configuration should be required to be done on the AWS side. The initial deployment on AWS should be done automatically using the AWS command line scrips and all subsequent updates should be handled automatically through dokku / git push / heroku php buildpack.
Use laradock/aws/ (see below) AWS elasticbeanstalk command line to deploy all needed laradock docker containers images to AWS (don't do any manual step like don't do FTP or any similar manual upload - All initial AWS deploy should work automatically through the AWS elasticbeanstalk command line)
Once deployed to AWS ...
Laravel - change and then do git push to the default "hello world" Laravel started app (/lara-admin) entry point and then refresh the browser's AWS production corresponding https://apps.domain.com/lara-admin/ URL and make sure the changed Laravel hello worlld version is served (dokku / heroku-build-pack should deploy / refresh the new PHP code automatically - without having to manually upload any PHP file)
WordPress - change and then do git push to Sage9's index.blade.php https://github.com/roots/sage/blob/master/resources/views/index.blade.php and then refresh the browser's AWS production corresponding https://apps.domain.com URL and make sure the updated page is coming
Step 1 - Have http://laradock.io/getting-started/#installation pre-requisites in-place
Step 2 - Use Laradock / Docker to setup a WordPress LAMP stack
A. Get the standard laradock Adminer and AWS (laradock/aws/ is required to get AWS elasticbeanstalk which adds support to automatically deploy to AWS using command line) (instead of laradock/aws/elasticbeanstalk you can also try AWS command line tools or AWS ECS command line tools, if more appropriate).
For initial AWS deployment use
- Use the AWS Elastic Beanstalk Command Line Interface (EB CLI) - https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3.html or
- AWS command line tools or
- AWS ECS command line tools - whichever is more appropriate.
B. Starting from the standard WordPress docker image alter that image and remove the linese which download wordpress.tar.gz file (ENV WORDPRESS_VERSION 4.9.2 and the curl command afterwards)
On the modified "php-wordpress-ready" image install PHP Composer tool (for dependency management in PHP)
Here is the official WordPress Docker image - https://hub.docker.com/_/wordpress/
Step 3 - On the above PHP/Composer image install roots.io's Bedrock WordPress project boilerplate
which allows managing the WordPress install and plugins using Composer
Step 4 - Using Composer install Laravel inside the Bedrock's /web/app/lara-admin folder (lara-admin parent's folder should be Bedrock's /web/app/ folde) - see Bedrock folder structure for more details - https://roots.io/bedrock/
Step 5 - Install roots.io's Sage 9 WordPress Theme on the same PHP/Composer image
Step 6 - Install dokku on the PHP image (remember the PHP image was altered to support dokku)
http://dokku.viewdocs.io/dokku/getting-started/installation/
Step 7 - Configure whatever is required to get the required permalink structure working fine
https://apps.domain.com (WordPress should be available here - Sage 9 theme)
https://apps.domain.com/wp-admin (WordPress admin should be available here)
https://apps.domain.com/lara-admin (Laravel "hello world" started app app should be available here)
Remember WordPress, Laravel and Adminer should be pre-installed / pre-configured. No manual steps should be required once the docker containers are started. Adminer should be pre-configured to connect to the WordPress database.