Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of noreply@sourceforge.net
 designates 216.34.181.60 as permitted sender)
Content-Type: multipart/related;
 boundary="===============0733067461465430202=="
MIME-Version: 1.0
To: allura-dev@incubator.apache.org
From: "Tim Van Steenburgh" <vansteenburgh@users.sf.net>
Reply-To: "[allura:tickets] " <7135@tickets.allura.p.re.sf.net>
Subject: [allura:tickets] #7135 Move our published docs to
 forge-allura.apache.org
Message-ID: 
 </p/allura/tickets/7135/eb41be6ec26e7b48de926fab809ab7cc6b2d72e0.tickets@allura.p.sourceforge.net>
In-Reply-To: <52f29222b9363c505e427ab0.tickets@allura.p.sourceforge.net>
References: <52f29222b9363c505e427ab0.tickets@allura.p.sourceforge.net>
Date: Mon, 17 Mar 2014 20:53:17 +0000

--===============0733067461465430202==
Content-Type: multipart/alternative;
 boundary="===============6654892619546136394=="
MIME-Version: 1.0

--===============6654892619546136394==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

- **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.
--===============6654892619546136394==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<div class="markdown_content"><ul>
<li><strong>status</strong>: open --&gt; closed</li>
<li><strong>assigned_to</strong>: Tim Van Steenburgh</li>
<li><strong>Size</strong>:  --&gt; 2</li>
<li><strong>Milestone</strong>: forge-backlog --&gt; forge-mar-21</li>
<li><strong>Comment</strong>:</li>
</ul>
<p>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. <code>deploy.sh</code> has been updated to build and deploy docs when new commits are pushed.<br />
</p>
<hr />
<p><strong> <a class="alink" href="http://sourceforge.net/p/allura/tickets/7135/">[tickets:#7135]</a> Move our published docs to forge-allura.apache.org</strong></p>
<p><strong>Status:</strong> closed<br />
<strong>Milestone:</strong> forge-mar-21<br />
<strong>Labels:</strong> asf <br />
<strong>Created:</strong> Wed Feb 05, 2014 07:33 PM UTC by Dave Brondsema<br />
<strong>Last Updated:</strong> Wed Feb 05, 2014 07:33 PM UTC<br />
<strong>Owner:</strong> Tim Van Steenburgh</p>
<p>Our docs are currently published to <a href="http://allura.sourceforge.net/docs/">http://allura.sourceforge.net/docs/</a> via a post-commit job on a SourceForge internal jenkins instance.</p>
<p>We should publish the docs on our Apache site, perhaps at a URL like <a href="https://forge-allura.apache.org/p/allura/docs/" rel="nofollow">https://forge-allura.apache.org/p/allura/docs/</a> (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.</p>
<p>We should move the post-commit publish to the Apache Jenkins job at <a href="https://builds.apache.org/job/Allura/" rel="nofollow">https://builds.apache.org/job/Allura/</a> or perhaps to the updating cron on the allura-vm host.</p>
<p>Lastly, we'll want <a href="http://allura.sourceforge.net/docs/">http://allura.sourceforge.net/docs/</a>* to redirect to the new locations.</p>
<hr />
<p>Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to <a href="https://sourceforge.net/p/allura/tickets/">https://sourceforge.net/p/allura/tickets/</a></p>
<p>To unsubscribe from further messages, a project admin can change settings at <a href="https://sourceforge.net/p/allura/admin/tickets/options.">https://sourceforge.net/p/allura/admin/tickets/options.</a>  Or, if this is a mailing list, you can unsubscribe from the mailing list.</p></div>
--===============6654892619546136394==--

--===============0733067461465430202==--