-
Notifications
You must be signed in to change notification settings - Fork 991
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
zola serve
with --output-dir
stopped serving assets in v0.18.0
#2423
Comments
Can confirm this, with 0.18 for Windows. The files are actually present in the output directory, but not loaded. Ignore the latter re Linux: I accidentally used 0.17 (system installed). This might be another issue, TBC. |
This is fixed by #2398, it would be nice to have a patch release with the fix. |
There's probably going to be a new release anyway since pulldown_cmark was updated |
A workaround for this problem is to give the absolute path of the output directory on the command line, ie instead of |
This didn't solve it on Windows - and I always use the full path to a ramdisk. Current next with #2398 fails to run for me on Windows, further comments will follow in that thread. My earlier comment re Linux can be ignored BTW. I usually write on Windows and compile on Linux. I forget |
@wold5 You'd need to format the path exactly like |
Would https://crates.io/crates/normpath solve the issue? |
Bug Report
Environment
Zola version: v0.18.0
Expected Behavior
zola serve --output-dir docs
should render the page normally, just likezola serve
(i.e., with no custom--output-dir
). That's how it worked in 0.17.2.Current Behavior
The HTML is served correctly, but all assets - including CSS and image files - result in 404.
Step to reproduce
zola serve
. The website looks normal.zola serve --output-dir docs
. The website looks broken, as the CSS is not there.The text was updated successfully, but these errors were encountered: