Update README

Author: LukeMcCann

README.md

@@ -1,11 +1,25 @@
-# docker-compose-laravel
-Simplified LEPP stack for local development.
+# Microservices 
 
-# Note
-Create a docker volume called 'data-postgres' before spinning up the container
+A secondary README.md is available in the `src/` folder showing the
+steps taken. 
 
-This is a workaround for an issue in which postgres permissions no longer allow
-for the data to be persisted over volumes.
+# Setup
+1. Ensure Docker is installed
+2. Run command: 
+    `docker volume create data-postgres`
+
+This is a workaround for an issue in which postgres does not allow
+for volumes to be shared due to postgres permissions. 
+
+3. `cd` into the root directory
+4. Run `docker-compose up`
+
+The server will appear via the url: [http://localhost:8080](http://localhost:8080)
+
+# Constructed Compose File
+LEPP development stack.
+
+This development stack
 
 ## Usage
 
@@ -25,3 +39,5 @@ Containers created and their ports (if used) are as follows:
 - **npm**
 - **composer**
 - **artisan**
+- **rabbitmq_management** - `:15672`
+- **rabbitmq** - `:5672`

src/README.md

@@ -1,3 +1,40 @@
+# Microservices
+
+## Project Steps
+
+1. Created Dockerfile for php - this enables the install and enable of specific tools: vi, pdo, xdebug
+
+Note: This would require changes for deployment as Postgres saves credentials based on OS anyone who accesses the container is able to make changes, this would require additional authentication along with the removal of `bash` from the used images to prevent unwarranted access to the container. 
+
+2. Created `docker-compose.yml` in this file the containers are set up (see README.md in root).
+
+This is conducted to ensure the environment is reproducible. In this example I modified the LAMP stack I usually use to instead utilise postgres over MySQL, along with the addition of containers for additional technologies: RabbitMQ.
+
+3. Created docker volume - this is a workaround, usually I would add a volume in the compose file linked to a directory within the root, this folder would be ignored by .gitignore, however, postgres does not allow for this, instead, the data is persisted in a volume and the database populated through a .sql file. 
+
+4. Created SQL for creation of database, and data population. 
+
+5. Created Models for the database tables
+
+6. Create Controllers for each model. 
+
+Utilising object oriented programming each of these is done through a class, due to some issues, mentioned below, this is the further milestone in a 2 hour period. 
+
+## Occuring Issues
+
+1. Postgres does not allow dir/data:db/data - workaround to use a docker volume instead.
+
+2. Postgres security concern - this would have to be rectified in a deployment image to ensure only warranted access is permitted due to postgres policies. 
+
+3. RabbitMQ starts without enabled plugins - as a workaround a enabled file was created and added via the volume: `./rabbitmq/enabled_plugins:/etc/rabbitmq/enabled_plugins` to ensure the necessary plugins were enabled at startup.
+
+## Next
+In continuation of this project I would first set up controllers for each model, furthermore I would first focus on developign the foreign service to send data to the microservice. 
+
+From here the microservice should then check the received payload type, this should then route the informaiton to the correct microservices only. Using RabbitMQ this service would be the producer, the other services would act as consumers picking up the information from RabbitMQ based on the provided ruleset. 
+
+More experience is required utilising RabbitMQ and Lumen before stepping to the next section. As such, I will continue working on these skills as I have not experienced these technologies before now.
+
 # Lumen PHP Framework
 
 [![Build Status](https://travis-ci.org/laravel/lumen-framework.svg)](https://travis-ci.org/laravel/lumen-framework)