We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Github pages can access foo.html by url /foo see https://rsp.github.io/gh-pages-no-extension/test1
/foo
I want lume server to work the same way.
currently this is my solution:
// config.ts import { Middleware } from "lume/core.ts"; const github_pages: Middleware = async (req, next) => { const response = await next(req); if(response.status !== 404) { return response; } const req2 = new Request(req.url + ".html", req); return next(req2); } const site = lume({ dest: './docs', prettyUrls: false, server: { middlewares: [github_pages], } });
It would be smarter if lume had a server option and could scan resources in core/server.ts
core/server.ts
The text was updated successfully, but these errors were encountered:
This requires also some changes in the way the page url variable is builded.
lume/core/filesystem.ts
Lines 218 to 223 in bc8412d
I think it's good idea but need to think the best way to implement it.
Sorry, something went wrong.
Added support for GitHub server style #193
f78586d
Implement no-html-extension #193
bc76328
I've implemented another option for prettyUrls to omit the .html extension but without saving the files as /index.html. It can be enabled with:
prettyUrls
.html
/index.html
const site = lume({ prettyUrls: "no-html-extension", });
and will be available in Lume 1.9.0.
No branches or pull requests
Github pages can access foo.html by url
/foo
see https://rsp.github.io/gh-pages-no-extension/test1
I want lume server to work the same way.
currently this is my solution:
It would be smarter if lume had a server option and could scan resources in
core/server.ts
The text was updated successfully, but these errors were encountered: