From ab3a92309283466fa1981a693b2f3e5ddb698d37 Mon Sep 17 00:00:00 2001 From: Kathryn Anne S Tan Date: Fri, 26 Jul 2024 22:24:03 +0300 Subject: [PATCH] Update the Readme.md to mention the move to the use of upstream image, while still using fly-apps/laravel-docker Dockerfile logic --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cacaefb..9c8ccdd 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ The Dockerfile generated by this project aims to provide support for: 4. Running the [Scheduler](https://laravel.com/docs/10.x/scheduling#running-the-scheduler) for your background tasks 5. Generating [Fly.io](https://fly.io/) relevant scripts essential for deploying your application as a Laravel Fly App, if applicable -The Dockerfile generated has been updated to merge with the Dockerfile logic found in https://github.com/fly-apps/laravel-docker. This change has been made to allow the use of an upstream image while still providing the base logic provided by the previously used image, `fideloper/fly-laravel`, which is maintained by that repositor. Further, it now visibly provides the necessary configuration files in the user's project directory, in the `.fly` folder, allowing the user full control over these files! +The Dockerfile generated has been updated to merge with the Dockerfile logic found in https://github.com/fly-apps/laravel-docker. This change has been made to allow the use of an upstream image while still providing the base logic provided by the previously used image, `fideloper/fly-laravel`, which is maintained by that repository. Further, it now visibly provides the necessary configuration files in the user's project directory, specifically in the `.fly` folder, finally allowing the user full control over these files! ### Installation