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

Suggestion: use .conf instead of .toml as extension for configuration #19

Closed
pkieltyka opened this issue Sep 24, 2015 · 5 comments
Closed

Comments

@pkieltyka
Copy link

TOML is great. I use it too, but I find the .conf extension is nicer and I've seen others do this as well.

@vdemeester
Copy link
Contributor

@pkieltyka thanks for the issue. I think this is not really a problem as you can specify a configuration file with any extension, so : traefik my.conf will work as long as it's a valid toml file and traefik configuration file.

From my point of view it's just a matter of samples but that's all.

/cc @emilevauge

@pkieltyka
Copy link
Author

sure, but usually people adopt conventions you lay out in your README. it was just a suggestion, I'm just an observer.

@vdemeester
Copy link
Contributor

@pkieltyka yeah that's what I though 😉. I'm fine to add a little thingy in the README to say .conf or .toml or … is ok, but I'll let @emilevauge give his opinion 😝.

@emilevauge
Copy link
Member

emilevauge commented Sep 24, 2015

Hi,
As seen in issue #7 (comment), I would like to integrate viper to manage configuration files. It will then be possible to provide an YAML, TOML or json configuration file to suit your needs. It appears that it will be difficult to change the extension :)

@pkieltyka
Copy link
Author

yuck

@emilevauge emilevauge modified the milestone: 1.0 Feb 27, 2016
m3co-code pushed a commit to m3co-code/traefik that referenced this issue Aug 22, 2017
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants