You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Marshall Schor (JIRA)" <ji...@apache.org> on 2010/12/11 03:35:00 UTC
[jira] Created: (INFRA-3284) add extra directory level to top of
pub-sub
add extra directory level to top of pub-sub
-------------------------------------------
Key: INFRA-3284
URL: https://issues.apache.org/jira/browse/INFRA-3284
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: SvnPubSub
Reporter: Marshall Schor
For the Apache UIMA project :-) - we would like a dual method to store stuff for our website - one which uses the pubsub method and requires all content come from SVN, and one where we can put "generated" information we want referenced from the website, in a place where it won't consume SVN resources needlessly (things like Javadocs for various releases).
This would have to be arranged so that the older-style method of transferring updates from people.a.o/www/uima.apache.org (before pubsub) worked for the part of our website not being done with pubsub.
Suggested directories:
www/uima.apache.org/pubsub/... for the pubsub stuff
www/uima-apache.org/non-svn/... for stuff we want to refer to but are not in svn (perhaps you can come up with a better name...)
(This last spot will hold more than just generated api javadocs)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3284) add extra directory level to top of
pub-sub
Posted by "Marshall Schor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970605#action_12970605 ]
Marshall Schor commented on INFRA-3284:
---------------------------------------
Thanks!
You make a good point about the non-pubsub dir name being in the URLs. Can you please rename it to be 1 character long, perhaps "d" (for "documentation")? Then our doc links would look like http://uima.apache.org/d/...
> add extra directory level to top of pub-sub
> -------------------------------------------
>
> Key: INFRA-3284
> URL: https://issues.apache.org/jira/browse/INFRA-3284
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: SvnPubSub
> Reporter: Marshall Schor
>
> For the Apache UIMA project :-) - we would like a dual method to store stuff for our website - one which uses the pubsub method and requires all content come from SVN, and one where we can put "generated" information we want referenced from the website, in a place where it won't consume SVN resources needlessly (things like Javadocs for various releases).
> This would have to be arranged so that the older-style method of transferring updates from people.a.o/www/uima.apache.org (before pubsub) worked for the part of our website not being done with pubsub.
> Suggested directories:
> www/uima.apache.org/pubsub/... for the pubsub stuff
> www/uima-apache.org/non-svn/... for stuff we want to refer to but are not in svn (perhaps you can come up with a better name...)
> (This last spot will hold more than just generated api javadocs)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-3284) add extra directory level to top of
pub-sub
Posted by "Marshall Schor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed INFRA-3284.
---------------------------------
Resolution: Fixed
Thank you very much for your quick response :-)
> add extra directory level to top of pub-sub
> -------------------------------------------
>
> Key: INFRA-3284
> URL: https://issues.apache.org/jira/browse/INFRA-3284
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: SvnPubSub
> Reporter: Marshall Schor
>
> For the Apache UIMA project :-) - we would like a dual method to store stuff for our website - one which uses the pubsub method and requires all content come from SVN, and one where we can put "generated" information we want referenced from the website, in a place where it won't consume SVN resources needlessly (things like Javadocs for various releases).
> This would have to be arranged so that the older-style method of transferring updates from people.a.o/www/uima.apache.org (before pubsub) worked for the part of our website not being done with pubsub.
> Suggested directories:
> www/uima.apache.org/pubsub/... for the pubsub stuff
> www/uima-apache.org/non-svn/... for stuff we want to refer to but are not in svn (perhaps you can come up with a better name...)
> (This last spot will hold more than just generated api javadocs)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3284) add extra directory level to top of
pub-sub
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970784#action_12970784 ]
Gavin commented on INFRA-3284:
------------------------------
Ok thats done.
> add extra directory level to top of pub-sub
> -------------------------------------------
>
> Key: INFRA-3284
> URL: https://issues.apache.org/jira/browse/INFRA-3284
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: SvnPubSub
> Reporter: Marshall Schor
>
> For the Apache UIMA project :-) - we would like a dual method to store stuff for our website - one which uses the pubsub method and requires all content come from SVN, and one where we can put "generated" information we want referenced from the website, in a place where it won't consume SVN resources needlessly (things like Javadocs for various releases).
> This would have to be arranged so that the older-style method of transferring updates from people.a.o/www/uima.apache.org (before pubsub) worked for the part of our website not being done with pubsub.
> Suggested directories:
> www/uima.apache.org/pubsub/... for the pubsub stuff
> www/uima-apache.org/non-svn/... for stuff we want to refer to but are not in svn (perhaps you can come up with a better name...)
> (This last spot will hold more than just generated api javadocs)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3284) add extra directory level to top of
pub-sub
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970580#action_12970580 ]
Gavin commented on INFRA-3284:
------------------------------
Ok this is now done and working fine.
On mino you now have:
/x1/www/uima.apache.org/pubsub/* which is your normal svnwc owned stuff for svnpubsub.
/x1/www/uima.apache.org/various/* which is your apbackup:uima accessible directory and rsyncs every hour as is the old way.
I've changed the httpd config so that /pubsub/ is the new documentroot and therefore does not break any incoming links etc.
To everyone is still looks and behaves like the site did without /pubsub/ directory. You need do nothing at your end to continue
using svnpubsub as you have been, so do not adjust your svn site directory.
You may introduce new directories/files into /x1/www/uima.apache.org/various and they will be accesible in between 1-2 hours
live, or right away if you use mino IP as proxy to your browser for checking.
To access anything inside /various/ online , goto http://uima.apache.org/various/ - I put a crappy index.html in there as a sample.
Let me know if you want /various/ directory renaming to something else. We do not need to rename /pubsub/ directory as it is not
in the url space anyway.
Please resolve this issue if/when you are happy with it.
> add extra directory level to top of pub-sub
> -------------------------------------------
>
> Key: INFRA-3284
> URL: https://issues.apache.org/jira/browse/INFRA-3284
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: SvnPubSub
> Reporter: Marshall Schor
>
> For the Apache UIMA project :-) - we would like a dual method to store stuff for our website - one which uses the pubsub method and requires all content come from SVN, and one where we can put "generated" information we want referenced from the website, in a place where it won't consume SVN resources needlessly (things like Javadocs for various releases).
> This would have to be arranged so that the older-style method of transferring updates from people.a.o/www/uima.apache.org (before pubsub) worked for the part of our website not being done with pubsub.
> Suggested directories:
> www/uima.apache.org/pubsub/... for the pubsub stuff
> www/uima-apache.org/non-svn/... for stuff we want to refer to but are not in svn (perhaps you can come up with a better name...)
> (This last spot will hold more than just generated api javadocs)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.