Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker Composer filename conflicts with production file #756

Open
DarkGhostHunter opened this issue Nov 21, 2024 · 0 comments
Open

Docker Composer filename conflicts with production file #756

DarkGhostHunter opened this issue Nov 21, 2024 · 0 comments

Comments

@DarkGhostHunter
Copy link

Sail Version

1.38.0

Laravel Version

11.33.2

PHP Version

8.4.0

Operating System

Linux

OS Version

Fedora 41

Description

When using the DevContainer version of Laravel Sail, and publishing the docker-compose.yml file, this action will may collide with another production-ready Docker Compose file and replace it contents.

There should be an option to use a non-standard name for the docker-compose.yaml, like docker-compose.development.yml or docker-compose.sail.yml.

Steps To Reproduce

  1. Create a docker-compose.yml file with the contents DO NOT REPLACE.
  2. Execute php artisan sail:publish
  3. Check the contents of the docker-compose.yml - It gets replaced, which is wrong.
@DarkGhostHunter DarkGhostHunter changed the title Use alternative docker-compose location to not conflict with production Docker Composer filename conflicts with production file Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant