<?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:"getting-started"</description><language>en</language><lastBuildDate>Mon, 15 Feb 2016 18:31:52 -0000</lastBuildDate><item><title>Incorrect Content-Type on first CSS requests, causing CSS not to be used</title><link>https://forge-allura.apache.org/p/allura/tickets/7971/</link><description>I can't pull up an example right now unfortunately since it's only occasional.  I think the URLs are the ones with `_ew_` in the path.

And then if the response gets cached, then subsequent page loads still don't work either.

[#7028] was for the same issue, so see that for additional details.  That ticket just resulted in a workaround, but its not great (especially if it gets cached).  This ticket is for a real fix.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 05 Oct 2015 14:07:47 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7971/</guid></item><item><title>Easy SVN hosting without recusion patch</title><link>https://forge-allura.apache.org/p/allura/tickets/7940/</link><description>Allura should be able to run SVN repos without patching SVN to handle deep recursion of repo folders. 

See &lt;http://mail-archives.apache.org/mod_mbox/allura-dev/201507.mbox/%3CDB4PR06MB0942864A70BEA90BED64044B97810%40DB4PR06MB0942.eurprd06.prod.outlook.com%3E&gt; thread.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 27 Jul 2015 19:13:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7940/</guid></item><item><title>Create a docker image for Allura</title><link>https://forge-allura.apache.org/p/allura/tickets/7806/</link><description>http://blog.dscpl.com.au/2014/12/hosting-python-wsgi-applications-using.html has a good starting point.

Would be nice to support development config (supplanting our Vagrant image) as well as a production-ready config (for which we don't have any good docs/images currently)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7806/</guid></item><item><title>`paster setup-app` should index users &amp; projects</title><link>https://forge-allura.apache.org/p/allura/tickets/7797/</link><description>Now that we have an interface at /nf/admin to search users and projects we should have them all indexed by default.  The ReindexUsers and ReindexProjects tasks should be run as part of `paster setup-app` (`bootstrap.py`)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 12 Jan 2015 15:42:43 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7797/</guid></item><item><title>Review &amp; update scm_host docs</title><link>https://forge-allura.apache.org/p/allura/tickets/7316/</link><description>User in IRC had issues with the scm_host docs not working

* We need to specify to install Apache
* default repo is code-0 and not git?  if so, update examples.  Might be best to force its mount point to "git" which is nicer anyway
* run through the rest of the instructions and make sure it works.  User was getting "fatal: http://localhost/git/p/test/git/info/refs not found: did you run git update-server-info on the server?" when running the `git ls-remote` cmd.
* check port numbers, with apache &amp; paster.  E.g. need to add :8080 to 127.0.0.1?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7316/</guid></item><item><title>add_project form lists all tools, including several that won't work</title><link>https://forge-allura.apache.org/p/allura/tickets/7309/</link><description>The add_project form lists all possible tools, including some that are deprecated, only work for user-projects, etc.

* Profile: only works for user-projects
* Tool: don't know what this is
* admin: should install by default, doesn't need to be listed
* userstats: only works on user-projects
* Tool: don't know what this is
* home: is old &amp; deprecated (can hide it via entry point disable in .ini)

Some others maybe should be considered optional and not too useful to show on the creation page, like URL shortener, External link.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7309/</guid></item><item><title>Make index page better</title><link>https://forge-allura.apache.org/p/allura/tickets/7308/</link><description>We should remove from the index page the non-functional category browsing on the left sidebar (and all the supporting code behind it - `ProjectCategory` iirc).

It'd also be good to have some welcoming content about how neighborhoods work, and pointers to adding/removing them, etc.  Se also [#5943]</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 15 Feb 2016 18:31:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7308/</guid></item><item><title>Post-setup instructions</title><link>https://forge-allura.apache.org/p/allura/tickets/5943/</link><description>After README, there are a lot of things to do to really get started, which aren't explained:

* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project:  `db.project.remove({shortname:'test'})    // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)


Several of these are explained in default wiki content now.


docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 10 Aug 2015 15:21:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5943/</guid></item></channel></rss>