incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Van Steenburgh" <>
Subject [allura:tickets] #7135 Move our published docs to
Date Mon, 17 Mar 2014 20:53:17 GMT
- **status**: open --> closed
- **assigned_to**: Tim Van Steenburgh
- **Size**:  --> 2
- **Milestone**: forge-backlog --> forge-mar-21
- **Comment**:

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 to forge-allura.a.o/p/allura/docs. `` has been updated
to build and deploy docs when new commits are pushed.  


** [tickets:#7135] Move our published docs to**

**Status:** closed
**Milestone:** forge-mar-21
**Labels:** asf 
**Created:** Wed Feb 05, 2014 07:33 PM UTC by Dave Brondsema
**Last Updated:** Wed Feb 05, 2014 07:33 PM UTC
**Owner:** Tim Van Steenburgh

Our docs are currently published to 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
(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
or perhaps to the updating cron on the allura-vm host.

Lastly, we'll want* to redirect to the new locations.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message