Create 404 & 500 page

[coke]

perhaps using raku doc's 404 as a model, we need to add a 404 handler page instead of relying on the nginx handler.

Related to Raku/doc#4214

[finanalyst]

@coke there is a 404.html that is generated and is in the root directory, but it is not being served by NGINX. So, the default NGINX 404 handler needs changing.

[finanalyst]

Also look at new-raku 404

[coke]

See #171

[Altai-man]

There are templates for 404 and 500 errors fitting the design, please do use them: http://164.90.207.89:10010/baka

See https://github.com/Altai-man/docs.raku.org/blob/master/templates/404.crotmp and https://github.com/Altai-man/docs.raku.org/blob/master/templates/500.crotmp for templates.

[coke]

The 404 page is created in the build and the website is now using it. Note that it seems to follow the text of the original site more than the update here. I have some edits for that in mind.

I can add the website rules for the 500 error once that page is generated during the build.

[finanalyst]

The 404 currently used on the site is generated from a .rakudoc file, so it can be consistently edited.
The 404/500 pages suggested by @Altai-man are crotmp templates. Like the index.html page, these could be just hacked into structure-source pages like index.rakdoc.

But note the text on Altai-man's page 'this error is already been reported' What does this mean. How is it reported?

[coke]

Please see my suggested version in #178

[coke]

But note the text on Altai-man's page 'this error is already been reported' What does this mean. How is it reported?

I assume "it's in the logs"; we should definitely be reporting out on the logs, or at least investigating occasionally. Odds of getting a 500 on the static site are slim, though.

[finanalyst]

What changes did you want?

[coke]

What changes did you want?

The ones I submitted in the PR?

[finanalyst]

@coke I missed the PR request. Just approved.

[Altai-man]

But note the text on Altai-man's page 'this error is already been reported' What does this mean. How is it reported?

The idea was that the engine will be smart enough to, on replying to a 404/500 request, report the error somewhere so that we could check what broke or what's the URL in question someone couldn't access, hence the line.