Make server use clean urls

[danielmorena]

Grate work!
As a suggestion, make some kind of flag to serve pages without ".html"

[brewingcode]

Thanks for the suggestion! I might have a way to do this, even though serving pages as you describe isn't something a static site generator has any say in. It's totally up to the webserver that is serving the files.

One way you can cheese it (and I do this myself) is to create a src structure where each directory has a single index.pug file in it, so that the resulting output looks something like this:

# input to pug-pack
src/page/index.pug
src/another-page/index.pug

# output from pug-pack
dist/page/index.html
dist/another-page/index.html

Any normal webserver will be configured to serve these at /page/ and /another-page/.

I suppose a flag could be added that would automatically turn file.html in src into file/index.html during the templating, ie:

# input
src/page.pug
src/another-page.pug

# output
dist/page/index.html
dist/another-page/index.html

Hmm, lemme think about that.

[danielmorena]

If you're using webpack (i confess i didn't verified), is just a matter to raise a flag in the live server https://webpack.js.org/configuration/dev-server/#devserver-historyapifallback them keep .html and use an .htacces or equivalent depending on server. The idea is to avoid write both .html and without on the links The project is excellent, if you point me info about this, i can propose a pull request with this

…

On Mon, Aug 16, 2021 at 3:55 PM Alex ***@***.***> wrote: Thanks for the suggestion! I might have a way to do this, even though serving pages as you describe isn't something a static site generator has any say in. It's totally up to the webserver that is serving the files. One way you can cheese it (and I do this myself) is to create a src structure where each directory has a single index.pug file in it, so that the resulting output looks something like this: # input to pug-pack src/page/index.pug src/another-page/index.pug # output from pug-pack dist/page/index.html dist/another-page/index.html Any normal webserver will be configured to serve these at /page/ and /another-page/. I suppose a flag could be added that would automatically turn file.html in src into file/index.html during the templating, ie: # input src/page.pug src/another-page.pug # output dist/page/index.html dist/another-page/index.html Hmm, lemme think about that. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEQX24CRDFXWQFA664CSGLT5FNKJANCNFSM5CGNPA4Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

-- Daniel Morena skype / daniel.moura.morena

[brewingcode]

My aim is to produce a dist folder that is statically serve-able (ie, by most webservers, as well as serve-able straight out of a directory locally). Webpack would only serve urls its way while developing: once the dist is served any other way, webpack no longer has any sway, and there's a good chance urls will break, because webpack was doing url shenanigans during local development that are not longer being done when dist is served statically.

You're free to try shoe-horning webpack in somehow, but I just don't think it would be a good fit for this use case, because webpack just doesn't exist when files are served statically.