Dockerization and Small Adjustments

[l4rm4nd]

Please check if the PR fulfills these requirements

• The commit message follows our contribution guidelines
• This change does not contain any possible security vulnerabilities

What kind of change does this PR introduce?

• Containerize the application stack with Docker. Simplify the process of self-hosting.
• Add tel: hyperlink to the restaurant's phone number and a hyperlink to Google Maps for the restaurant's location.
• Adjust the readme to reflect the additions regarding Docker

What is the current behavior?

Application stack must be installed manually, barebone. Separate MariaDB database required too.

What is the new behavior?

Application stack can be spawned up using Docker Compose.

Does this PR introduce a breaking change?

The code adjustments and new files should not break existing instances when being updated.

Other things to mention?

You'll have to adjust the Docker image defined in the docker-compose.yml file if you want to provide an externally hosted Docker Image (e.g. from Dockerhub). Currently, my Docker Image is still referenced for testing purposes.

Currently, the npm build process is postponed to the Docker runtime, as the application code relies on production ready environment variables (especially NEXT_PUBLIC_IMAGEKIT_URL_ENDPOINT). I'll try some other methods to get an optimized production build ready during Docker Image build process. In the meantime, user just have to wait a few minutes until the docker container comes up, as the build process takes some time.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud