#7135 Move our published docs to forge-allura.apache.org

v1.0.0
closed
General
nobody
2015-08-20
2014-02-05
No

Our docs are currently published to http://allura.sourceforge.net/docs/ via a post-commit job on a SourceForge internal jenkins instance.

We should publish the docs on our Apache site, perhaps at a URL like https://forge-allura.apache.org/p/allura/docs/ (currently a redirect). We could do this by configuring that particular URL in Apache to serve from a directory instead of go to the allura wsgi app.

We should move the post-commit publish to the Apache Jenkins job at https://builds.apache.org/job/Allura/ or perhaps to the updating cron on the allura-vm host.

Lastly, we'll want http://allura.sourceforge.net/docs/* to redirect to the new locations.

Discussion

  • Tim Van Steenburgh

    • status: open --> closed
    • assigned_to: Tim Van Steenburgh
    • Size: --> 2
    • Milestone: forge-backlog --> forge-mar-21
     
  • Tim Van Steenburgh

    I left the /p/allura/docs Link tool installed, but repointed it to /docs, which is served statically. I disabled the SF jenkins allura-docs build and installed an .htaccess redirect from allura.sourceforge.net/docs to forge-allura.a.o/p/allura/docs. deploy.sh has been updated to build and deploy docs when new commits are pushed.

     
  • Dave Brondsema

    Dave Brondsema - 2014-03-18

    I was thinking the docs should go at /p/allura/docs rather than /docs, since they are part of the allura project rather than part of the whole forge. Perhaps a fuzzy distinction though since we're hosting on our own platform.