[
https://issues.apache.org/jira/browse/WHIMSY-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610400#comment-16610400
]
Sebb commented on WHIMSY-199:
-----------------------------
Turns out that the following works for logging but does not work well for
logging.html; it responds with 300 - Multiple choices:
{code}
ln -s Logging_Services.html logging
{code}
Whereas this works for both logging and logging.html:
{code}
ln -s Logging_Services.html logging.html
{code}
However this means that tag links can potentially clash with existing web pages.
I now wonder whether it might not be simpler to use Redirects as necessary to
support the required behaviour.
Either as local .htaccess entries or in the main HTTPD config.
The latter would require Infra Puppet changes; the former only a single upfront
Infra Puppet change to allow htaccess for the minutes directory.
> Also link to committee's minutes by 'tag' instead of 'display_name'
> -------------------------------------------------------------------
>
> Key: WHIMSY-199
> URL: https://issues.apache.org/jira/browse/WHIMSY-199
> Project: Whimsy
> Issue Type: Wish
> Components: Website
> Reporter: Henk Penning
> Priority: Major
>
> It would be nice if pages like :
> [https://whimsy.apache.org/board/minutes/Logging_Services]
> can (also) be referred to as
> [https://whimsy.apache.org/board/minutes/logging]
>
> In general, "link by [committee] tag" as opposed to "[committee]
> display_name",
> as given in https://whimsy.apache.org/public/committee-info.json
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
