Content "outside" of radiant

Hello All,
I’ve got radiant installed, running, etc.

I would like to serve up my own folders of stuff outside of radiant’s
control.
I’ve tossed a folder of stuff in /public/ but I get a 404 when I just
try to pull it up.
What is the proper way to do this?
Thanks,
BJ Clark

Because of the way most dispatcher setups work, you’ll have to provide a
fully-qualified url, not just a directory. Alternatively, you can tinker
with some of the rewrite rules (if you’re using Apache). I’m not
qualified to help you with mod_rewrite, however… it’s mostly a mystery
to me.

Sean C.
seancribbs.com

The hint is already inside of your /public/.htaccess file …

If you don’t want Rails to look in certain directories,

use the following rewrite rules so that Apache won’t rewrite

certain requests #

Example:

RewriteCond %{REQUEST_URI} ^/notrails.*

RewriteRule .* - [L]

Uncommented it would not dispatch anything under /notrails. Very
handy if you like to run Ruby and PHP on the same server for other
tasks.

  • Jon

On 12/12/2006, at 2:25 PM, BJ Clark wrote:

Hello All,
I’ve got radiant installed, running, etc.

I would like to serve up my own folders of stuff outside of
radiant’s control.
I’ve tossed a folder of stuff in /public/ but I get a 404 when I just
try to pull it up.
What is the proper way to do this?

BJ, It depends on what platform you are running on. Could you give us
a bit more info? eg. what webserver, using fast-cgi or not…

Bodhi