# Running non-root

**URL:** <https://www.ruby-forum.com/t/running-non-root/98305>\
**Category:** Radiant CMS\
**Created:** [July 13, 2006, 7:00pm UTC](https://www.ruby-forum.com/t/running-non-root/98305 "2006-07-13T19:00:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pond](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/7ab992/32.png) [@pond](https://www.ruby-forum.com/u/pond)\
**Post date:** [July 13, 2006, 7:00pm UTC](https://www.ruby-forum.com/t/running-non-root/98305/1 "2006-07-13T19:00:40Z")

</div>

As with many Rails applications, Radiant has the odd glitch when asked  
to run from a non-document root location. I’m serving Radiant from  
/rails/radiant at the moment. After the usual updates (prefix all  
routes, set asset\_host in environment.rb, set a unique cookie prefix  
there too to avoid collision with other apps on the same host)  
everything works, except \<r:link\>-generated links. These are created  
relative to the host document root.

I’m happy to fix this and produce a patch but after a brief look around  
and some head scratching I couldn’t quite figure out which files I  
should be changing… All pointers appreciated 🙂