Create dev.sh for managing local development

[alfiephillips]

• In correspondence to managing Development VS Production, we need a specific environment to manage the creation and disposal of containers; this could potentially occur after every commit or after every save. This is dependent on the need for a live update, which may be a potential issue and slowing us down for frontend development.

• Create a dev.sh file which should be run while debugging; testing new features; testing or configuring the environment. This file will be used to increase verbosity and log errors more frequently, while in production mode this will be silenced.

• Research the potential option for live updates while working inside a container to avoid reloading images and long build times - for example being able to append changes and only reload the image effected. (Hopefully this is possible otherwise we may need to defer to XAMPP)

• dev.sh should give an option to enter custom environment variables for testing and debugging, this will give us an easier path to finding the cause of exceptions during configuration ex: connection to the database.

This is a high priority issue before we start development

[alfiephillips]

Any ideas for live development similar to XAMPP @jakemackie ?

[alfiephillips]

Closing this issue as removing all processes including docker and reverting to using XAMPP server.