Skip to content

Commit 04849ae

Browse files
authored
Update README.md
1 parent ee0b713 commit 04849ae

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

README.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# PHP-FPM + Nginx + Composer + Laravel Docker Image
22

3-
This Docker image provides a production-ready environment for running Laravel and Statamic applications. It combines Nginx, PHP-FPM 8.3, and Supervisor in a single container, optimized for AWS ECS/Fargate deployment.
3+
This Docker image provides a production-ready environment for running Laravel and Statamic applications. It combines Nginx, PHP-FPM 8.3, and Supervisor in a single container.
44

55
## Image Components
66

@@ -54,8 +54,7 @@ The image implements a comprehensive logging strategy optimized for container en
5454
This logging setup ensures:
5555
- All logs are properly captured in container environments
5656
- Compatibility with AWS CloudWatch
57-
- No log file rotation issues in containers
58-
- Proper error tracking without exposing sensitive information
57+
5958

6059
### 5. Health Checks
6160
- Built-in health check endpoint at `/healthz`
@@ -68,7 +67,7 @@ This logging setup ensures:
6867
- Listens on port 8080
6968
- Configured for Laravel/Statamic routing
7069
- Includes health check endpoint
71-
- Optimized for PHP-FPM communication
70+
7271

7372
### Supervisor Configuration
7473
- Runs in foreground mode (PID 1)
@@ -94,4 +93,4 @@ The application can be configured using standard Laravel environment variables.
9493

9594
- The image is designed to run as a single container in production
9695
- All logs are properly forwarded to container logs
97-
- The setup is optimized for AWS ECS/Fargate deployment
96+
- The setup is optimizedg for AWS ECS/Fargate logging into Cloudwatch through awslogs driver.

0 commit comments

Comments
 (0)