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
To clarify, within m4b, our functions already explicitly pass the docker-compose.yaml file name when required. This ensures that the system is able to work with different compose file names. While docker-compose.yaml is our default file name for now, it is always explicitly passed to avoid any ambiguity. Unless there has been an oversight, all functions should already be capable of supporting alternative file names.
Additionally, Docker's default behaviour uses docker-compose.yaml as the fallback if no need default filename file is found and no file name is explicitly provided, compose.yaml is the new designated default as you pointed out. However, since we explicitly pass the file name in m4b, this change in Docker defaults shouldn't affect its functionality.
If you've encountered an issue while running m4b related to the compose file, could you please share the steps to reproduce it? This will help us investigate further and ensure everything is functioning as intended.
Let me know if there's anything else you'd like clarified, or if I’ve missed any part of your request. We're always open to making improvements where needed!
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
<sarcasm>little</sarcasm>
change will require.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: