www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (INFRA-10688) unionfs for maven site merging between site and components documentation
Date Sat, 31 Oct 2015 15:39:27 GMT

    [ https://issues.apache.org/jira/browse/INFRA-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984025#comment-14984025
] 

Hervé Boutemy commented on INFRA-10688:
---------------------------------------

another idea: what if we published components documentation to CMS staging area?

I tried, but when CMS builds then checks result in, it deletes content

(and we already used CMS extpaths.txt in the past to merge content when publishing to production
area, but we stopped since we had too much content in extpats.txt then it took 1 hour for
CMS to publish content to production area)

could it be possible for the CMS not to delete some content from svn staging area?
(of course if easier than unionfs)

> unionfs for maven site merging between site and components documentation
> ------------------------------------------------------------------------
>
>                 Key: INFRA-10688
>                 URL: https://issues.apache.org/jira/browse/INFRA-10688
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: CMS, SvnPubSub, Website
>         Environment: http://maven.apache.org/
>            Reporter: Hervé Boutemy
>
> Maven site is composed of a main site + components documentation: http://maven.apache.org/developers/website/website-overview.html
> Currently it is done with 2 svnpubsub entries + .htaccess:
> - / is https://svn.apache.org/repos/infra/websites/production/maven/content/ and /components
is https://svn.apache.org/repos/infra/websites/production/maven/components/, with following
svnwcsub.conf entries:
> /www/maven.apache.org/content: %(CMS)s/maven/content
> /www/maven.apache.org/content/components: %(CMS)s/maven/components
> - end of .htaccess rewrite rules https://svn.apache.org/repos/infra/websites/production/maven/content/.htaccess
rewrites to /components if file not found in /
> It works not so bad but there are 2 shortcomings:
> - wrong redirect for directories not ending with /: see http://maven.apache.org/ref
> - download.cgi script (for mirrors) does not work: try "download" link from http://maven.apache.org/ant-tasks/index.html
> After looking for solutions for these shortcomings, I found that in fact, what we are
trying to do with .htaccess rewrite rules would in fact be perfectly done with something like
an unionfs (or any equivalent tool) that merges /components into /
> This would solve both shortcomings and be less cryptic than the .htaccess rewrite rules
> could such unionfs be configured for http://maven.apache.org/ , please?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message