config.toml isn't read by default

[drewwells]

Creating a new site and starting it hugo server -t slim --buildDrafts gives errors unable to find config.

Error:

hugo server -t slim --buildDrafts
ERROR: 2015/08/18 Unable to locate Config file. Perhaps you need to create a new site. Run `hugo help new` for details
ERROR: 2015/08/18 No 'baseurl' set in configuration or as a flag. Features like page menus will not work without one.

Adding this to the server call fixes the issue. --config=config.toml

[drewwells]

Reproduced on dac9c0d

[anthonyfok]

Same problem here, though hugo at dac9c0d was working just fine several days ago.

It turns out that the Viper's way of searching config file handling was changed two days ago:

• Current directory used for config if no other specified directories exist spf13/viper#73: Current directory used for config if no other specified directories exist.

Thankfully, the author of the patch has included a note telling us how to get the old behaviour back: spf13/viper#73 (comment)

To get the pre-fix functionality back in your application, add the following call the proper viper callee > after adding all other search paths to it:

viper.AddConfigPath(".")

This fix works for me. Will commit a fix soon. :-)

[drewwells]

Fixed, thanks!

On Wed, Aug 19, 2015 at 1:43 AM Anthony Fok notifications@github.com
wrote:

Closed #1363 #1363 via 4047ca5
4047ca5
.

—
Reply to this email directly or view it on GitHub
#1363 (comment).

[akbarsha03]

After I create the site I forgot to navigate to the newly created directory on my command prompt which caused the issue

[github-actions]

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.