<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for labels:docs AND status:open</description><language>en</language><lastBuildDate>Thu, 22 Oct 2015 19:31:36 -0000</lastBuildDate><item><title>Set up maintenance command to clean 'notification' collection</title><link>https://forge-allura.apache.org/p/allura/tickets/8009/</link><description>The records in the `notification` collection do not need to stick around forever.  It'd be good to have a paster command to clean up old ones, and documentation about setting up a cron job for it.  Even better if we can think of a smart way to handle it automatically within allura, so a cron job wouldn't be necessary.  Here's the basic query:

    db.notification.remove({pubdate:{$lt: new Date(Date.now() - 1000*60*60*24*31*2)}})</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 22 Oct 2015 19:31:36 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8009/</guid></item><item><title>More activity stream docs</title><link>https://forge-allura.apache.org/p/allura/tickets/7252/</link><description>Write more docs about Activity Streams, both the library and how it works with Allura.  Think high-level and make sure we cover a view of the whole system.  Perhaps make a guide section in here http://allura.sourceforge.net/docs/#developing-allura</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Fri, 07 Mar 2014 19:22:16 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7252/</guid></item><item><title>install instructions should have 'curl' as dependency package, and clarify scm.repos.root</title><link>https://forge-allura.apache.org/p/allura/tickets/2313/</link><description>*Originally created by:* tesch

Working through getting Allura setup for the first time, just some minor tweaks to README.markdown :

- 'curl' package is needed by git commit hooks, could be added to the apt-get line

- the instructions could be more clear about the default location of the scm repository: from the install instructions it looks like they should be /git,/hg,/svn, but the default development.ini puts them in /tmp/...

(ps, big ups to you all.)
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 08 Apr 2015 22:55:12 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2313/</guid></item><item><title>Show examples of anon access for the REST API</title><link>https://forge-allura.apache.org/p/allura/tickets/1650/</link><description>Discussed on Jabber whether we want to allow anonymous (key-less) access to REST API, or whether we should require a key for any request. Dave confirmed that anon access is ok.

Our backend actually supports it:
https://sourceforge.net/rest/p/allura/home/

But REST API client we provide (both in-tree rest_api and dependency-free class used in some scripts) insist to be fed with key and secret, so that should be made optional.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Sokolovsky</dc:creator><pubDate>Mon, 01 Dec 2014 02:14:04 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1650/</guid></item></channel></rss>