[jira] Closed: (INFRA-3324) Export Confluence TAPESTRY as tapestry.apache.org

["#asfinfra IRC Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

#asfinfra IRC Bot closed INFRA-3324.
------------------------------------

    Resolution: Fixed

> Export Confluence TAPESTRY as tapestry.apache.org
> -------------------------------------------------
>
>                 Key: INFRA-3324
>                 URL: https://issues.apache.org/jira/browse/INFRA-3324
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Confluence, HTTP Server, Website
>            Reporter: Howard M. Lewis Ship
>
> We have recently converted our documentation process to be primarily centered on Confluence. We now have a bit of a Rube Goldberg system for getting content out of Confluence via its auto-export; it then gets copied to people.apache.org where I have this cron job running:
> > crontab -l
> 10 * * * * /usr/local/bin/rsync -rp /www/confluence-exports/TAPESTRY/ /www/tapestry.apache.org
> > 
> Later, /www/tapestry.apache.org is rsynced to the public facing directory served as tapestry.apache.org.
> This means it takes several rsync jobs to get a change in Confluence visible to the outside world. This means a delay of up to several hours.
> Would it be possible to set up an rsync job to copy directly from https://cwiki.apache.org/TAPESTRY/ to the public web site, once an hour?  That would cut two hops out of the Rube Goldberg machine.
> We still need the current rsync from people.apache.org for documentation generated by the build (JavaDoc, etc.).
> Thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.