[allura:tickets] #7135 Move our published docs to forge-allura.apache.org

[Tim Van Steenburgh <va...@users.sf.net>]

- **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 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.  



---

** [tickets:#7135] Move our published docs to forge-allura.apache.org**

**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 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.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.