From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ <censored>)]
Date: Tue, 05 Jul 2022 08:37:50 +1000 [thread overview]
Message-ID: <87y1x88poj.fsf@gmail.com> (raw)
In-Reply-To: <t9v7nq$mrh$1@ciao.gmane.io>
Max Nikulin <manikulin@gmail.com> writes:
>
> However it seems, Bastien earlier configured a set of rewrite rules mapping old file names
> with more lower case letters to new ones. In my opinion it is the best option and it
> should be restored. List of files may be committed to git (either Org or site) to detect
> changes later and to add new mappings when some file disappears.
Are you sure about that. There is nothing along these lines in the nginx
config file that I can see. Also, my reading following that thread you
provided earlier was that Bastien thought the overhead to manage such
lists was too high?
I guess we need to wait for Bastien to indicate his preference. I find
things a little challenging as there seems to be a fair bit of
outdated/conflicting information scattered through various files/notes.
At this point, my vote is to just do a basic updated 404 page that
points to the index.html page for orgmode.org so that users have
something to follow and not a big ugly 404 Not Found. The rest we can
consider later.
next prev parent reply other threads:[~2022-07-04 22:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:01 [BUG] The documentation webserver gives 404s [9.5.4 (release_9.5.4-3-g6dc785 @ <censored>)] Rudolf Adamkovič
2022-07-03 11:50 ` Ihor Radchenko
2022-07-03 12:23 ` Tim Cross
2022-07-03 14:01 ` Ihor Radchenko
2022-07-03 16:48 ` Max Nikulin
2022-07-03 21:30 ` Tim Cross
2022-07-04 12:10 ` Ihor Radchenko
2022-07-04 12:27 ` Tim Cross
2022-07-04 12:58 ` Ihor Radchenko
2022-07-04 17:24 ` Max Nikulin
2022-07-04 22:37 ` Tim Cross [this message]
2022-07-05 2:39 ` Max Nikulin
2022-07-05 2:54 ` Tim Cross
2022-07-05 4:22 ` Max Nikulin
2022-07-05 4:36 ` Tim Cross
2022-07-05 5:11 ` Ihor Radchenko
2022-09-18 9:06 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1x88poj.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).