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

Option to provide name for docker-compose.yaml for better dockge support #109

Open
BonzoFestoon opened this issue Dec 20, 2024 · 1 comment

Comments

@BonzoFestoon
Copy link

Is your feature request related to a problem? Please describe.

Using dockge on Raspberry Pi. Dockge looks for compose.yaml, not docker-compose.yaml

Describe the solution you'd like

  • Add a question to the end of the guided setup to provide a name other than the default docker-compose.yaml
  • Add support of the option is in the config files.
  • All the other things that this <sarcasm>little</sarcasm> change will require.

Describe alternatives you've considered

The only alt is to write a script to run once the yaml file has been generated by the guided setup.

Additional context

N/A
@MRColorR
Copy link
Owner

Thanks for your feedback and suggestions!

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!

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

2 participants