You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit introduces a complete Docker setup for deploying the OTE application on Render.com. It addresses the issue of a missing Dockerfile in the root directory, which caused deployment failures.
The main changes include:
- A new multi-stage `Dockerfile` in the root directory that builds a production-ready image with PHP-FPM and Nginx.
- A `render.yaml` file to define the deployment blueprint for Render, including a web service and a PostgreSQL database.
- Nginx configuration and a start script for the production environment.
- An updated `.dockerignore` file to optimize the Docker build context.
- Updated documentation in `docs/RENDER.md` to reflect the new deployment process.
Copy file name to clipboardExpand all lines: docs/RENDER.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,17 @@ This project is configured for automatic deployment to the [Render](https://rend
4
4
5
5
## How It Works
6
6
7
-
This repository contains a `render.yaml` file that uses Render's "Blueprint" feature. This file tells Render everything it needs to know to deploy the application, including:
7
+
This repository contains a `render.yaml` file in the root directory that uses Render's "Blueprint" feature. This file tells Render everything it needs to know to deploy the application, including:
8
8
9
-
- A **web service** running the Laravel application.
9
+
- A **web service** running the Laravel application. This service is built using the `Dockerfile` in the root of the repository.
10
10
- A **PostgreSQL database** for storing data.
11
11
12
12
When you push changes to the `main` branch on GitHub, Render will automatically:
13
13
14
14
1. Detect the changes.
15
-
2. Build the application using the `buildCommand` defined in `render.yaml`. This includes installing dependencies and running database migrations.
16
-
3. Deploy the new version of the application.
15
+
2. Build the Docker image for the application.
16
+
3. Run the `buildCommand` defined in `render.yaml` to execute database migrations (`php artisan migrate --force`).
0 commit comments