Zola version: Github master branch
OS: Linux
Tell us what should have happened.
Running zola init in an empty directory should initialize the directory.
Tell us what happens instead of the expected behavior. If you are seeing an
error, please include the full error message and stack trace. You can get the
stacktrace of a panic by addingRUST_BACKTRACE=1when running azolacommand.
Example run:
$ RUST_BACKTRACE=1 ../zola/target/debug/zola init
Welcome to Zola!
Please answer a few questions to get started quickly.
Any choices made can be changed by modifying the `config.toml` file later.
> What is the URL of your site? (https://example.com):
> Do you want to enable Sass compilation? [Y/n]:
> Do you want to enable syntax highlighting? [y/N]:
> Do you want to build a search index of the content? [y/N]:
Failed to create the project
Error: File exists (os error 17)
As you see, the initialization fails with a "File exists" error. The error message could be improved to mention which file exists: it took some digging in the issues to figure out why it failed. (Running zola init mydir works, it's initializing the current empty dir that fails).
Please provide the steps to reproduce the issue.
If the issue is hard to reproduce, please provide a sample repository or sample
that triggers the bug.
Create an empty directory, go inside and run zola init.
I should have tried that before releasing ๐คฆโโ
In theory a very simple bugfix if anyone wants to try
@riginding fixed it in the next branch ๐
Awesome!
@Keats Do you know when will be the next release for newcomers to not meet this issue when launching Zola for the first time? :smiley:
No timeline yet, I want to have the non slugification for paths (on phone,
can't find the issue) in before releasing. I'll try to work on that next
week.
On Sat, 30 Nov 2019, 01:18 Allan Jacquet-Cretides, notifications@github.com
wrote:
Awesome!
@Keats https://github.com/Keats Do you know when will be the next
release for newcomers to not meet this issue when launching Zola for the
first time? ๐โ
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/getzola/zola/issues/814?email_source=notifications&email_token=AAFGDIYKY3HCCSI62ONBD2DQWGWMXA5CNFSM4I6HN5D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPV7YQ#issuecomment-559898594,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFGDI42J7PKJTJKBM3S6HDQWGWMXANCNFSM4I6HN5DQ
.
@Keats Would it be possible to have this fix released sooner? Without it, the out-of-the-box user experience for new users looking to initialize a new Zola project inside an existing Git repo is very poor. Thanks for all the effort in creating and maintaining this project!
There's a WIP feature in the next branch (the slugification), as soon as it gets finished it will be released. The basic version is already in there, it just needs to be polished
@Keats Awesome! Can't wait to try it out. Once the initial project directory is created, the rest of the user experience is much better. I'll gladly try out that branch and see how the slugification feature is faring.
I'm getting this error too compiling from master. I guess it hasn't been merged in from next yet?
It has been merged in next, not released yet. Try building the next branch
I see. Thanks @Keats!
I did manage to get it working by guessing the CLI argument structure (documentation? what documentation?), but haven't really found _Zola_ to be suitable for my use-case - hence I'm currently exploring alternatives.
For reference I want to build a simple static site for an open-source project of mine.
I did manage to get it working by guessing the CLI argument structure (documentation? what documentation?)
Is https://www.getzola.org/documentation/getting-started/cli-usage/#init not detailed enough? There are some improvements already in the next branch for that page: https://github.com/getzola/zola/blob/next/docs/content/documentation/getting-started/cli-usage.md
Ah, I see! I must have missed that.
Most helpful comment
@riginding fixed it in the
nextbranch ๐