-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Make hugo.toml the new config.toml #8979
Comments
Note that the old, e.g. config.toml, still works fine. See gohugoio#8979
Note that the old, e.g. config.toml, still works fine. See gohugoio#8979
Note that the old, e.g. config.toml, still works fine. See gohugoio#8979
If
I don't have an opinion about this, but it's something to think about. Thanks for all your great work bep and others! |
@nancym, it's still the hugo config. The goal is to make the file name less ambiguous in the context of a generic filesystem. The The |
@moorereason is right. My primary motivation behind this is to get to a state where _every Hugo project has a hugo.* file). So, if you have a |
Both will of course work, but hugo.toml will win if both are set. We should have done this a long time ago, of course, but the reason I'm picking this up now is that my VS Code setup by default picks up some JSON config schema from some random other software which also names its config files config.toml. Fixes gohugoio#8979
Both will of course work, but hugo.toml will win if both are set. We should have done this a long time ago, of course, but the reason I'm picking this up now is that my VS Code setup by default picks up some JSON config schema from some random other software which also names its config files config.toml. Fixes gohugoio#8979
Both will of course work, but hugo.toml will win if both are set. We should have done this a long time ago, of course, but the reason I'm picking this up now is that my VS Code setup by default picks up some JSON config schema from some random other software which also names its config files config.toml. Fixes #8979
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
So, the naming of Hugo's default config file
config.toml
(and json ...) was a mistake. The reasoning:I have looked at this before and just brushed it off with a "there are too many projects out there", but I now think we should just do it:
config.toml
will still be a fall back, but we first tryhugo.toml
.config.toml
case, but that is not in scope for now.hugo.toml
(or JSON ...) eventually be a requirement for any Hugo project (even if it's empty).The text was updated successfully, but these errors were encountered: