[TECH ED] Local Development Docker

### Link to the coursework

https://docs.docker.com/

### Why are we doing this?

#### Local development (bonus)
This step is a bonus one, if you completed all previous steps and are not behind on the previous weeks.

Dockerise your Frontend, and have it run locally alongside via Docker with your backend. Can you get both to work correctly at the same time?

Replicate the process for the database, and move it from your local instance to a local Docker Container (remember persistence via volumes).

In both cases, managed AWS services (S3 and RDS) give us a lot of advantages for Cloud Deployment, but lack support for local development, and Docker can help with that.

Imagine how you would automate, with a script, the process of rebuilding all 3 containers on changes, and restart/reconnect everything. Try to build it.

### How to get help

If you are doing this for the first time, **this will be hard**. You **must** reach out to volunteers to help you. Your ability to ask for help is actively assessed during this time. Ask good, curious questions with links, code samples, and no screenshots.

https://curriculum.codeyourfuture.io/guides/asking-questions/

You are **not** expected to be able to complete this module completely independently. You **are** expected to get help from volunteers.

### How to submit

In this advanced module you will demo your work. You may wish to make notes for case studies to add to your portfolio.

Start with the linked Docker coursework and inspect the existing frontend, backend, and database setup. Done means all three run locally in Docker, the database persists through volumes, the services work together, and a script can rebuild and reconnect them after changes.

Written by the indexing model from the issue text.