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
Currently, commands like serve, down, run use the current directory as working direcory. When a User is in a subdirectory, this might cause problems with mounting said subdirectory or not correctly removing containers.
A simple solution would be to check wether the current working directory contains a composer.json file and is not located under vendors/ (as modules are not a valid project in most cases).
A PR must fulfill the following:
when executing up, down, serve, exec or run in a project containing a composer file, everything works correctly
when executing up, down, serve, exec or run in a directory of a vendor module, a warning is thrown that ssdev is not intended for use in modules
when executing up, down, serve, exec or run in any other directory, a warning is thrown that no project could be found
The text was updated successfully, but these errors were encountered:
mleutenegger
changed the title
ssdev should check for the presence of a project before executing docker compose
Feature: when executing ssdev commands in subdirectories, there should be a warning when no project is present
May 21, 2022
Currently, commands like
serve
,down
,run
use the current directory as working direcory. When a User is in a subdirectory, this might cause problems with mounting said subdirectory or not correctly removing containers.A simple solution would be to check wether the current working directory contains a
composer.json
file and is not located undervendors/
(as modules are not a valid project in most cases).A PR must fulfill the following:
up
,down
,serve
,exec
orrun
in a project containing a composer file, everything works correctlyup
,down
,serve
,exec
orrun
in a directory of a vendor module, a warning is thrown that ssdev is not intended for use in modulesup
,down
,serve
,exec
orrun
in any other directory, a warning is thrown that no project could be foundThe text was updated successfully, but these errors were encountered: