-
Notifications
You must be signed in to change notification settings - Fork 180
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
[Proposal] Include way to handle 404 pages #60
Comments
Hey David! I wish this was that easy, but since it's a static site it has to be handled at the webserver level. If you use GitHub Pages, you can just create a For anyone else who finds this issue down the road, here's an example of how you might do it with nginx: https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-to-use-custom-error-pages-on-ubuntu-14-04 |
Duh. Was way over thinking this one. Thanks! |
Hi i tried ot crate a 404.html in the source folder, but it is not copy over during the build process. Any idea on how to copy this file ? EDIT: found it, pipe this line in your gulpfile.js
EDIT: |
I think that's probably an issue of pretty URLs being enabled by default so your file is ending up at /build_github/404/index.html Might be a way to disable that per page if you're clever 🤔 |
@chrisvidal Make sure that One thing you might change is to append a
|
thank @damiani whenI follow manually the content of the folder build_github/ I can see the 404.html first then it is removed.
Is it because my command line is like this ?
|
Another way you can do it, if you have pretty URLs enabled, is to name your |
Interesting idea, I am using github pages, let's see if it can support this Well i guess i will have to forget the idea of handling the 404 error |
Not sure if I'm just overlooking the section in the documentation or through my trials through the code, but would be cool to handle missing pages with a
404.blade.php
file or something when those errors occur.Was thinking along the lines of how Laravel uses the errors folder for those views, though not entirely certain how to implement it yet at this point.
The text was updated successfully, but these errors were encountered: