What you've discovered is unfortunately one of Radiant's shortcomings. Radiant expects to be deployed at the root of your particular domain.
If you want to deploy it into a subdirectory, there is no easy way. You gonna have to update a lot of files to point to the new subdirectory (things like css, js, and many others). It's not hard, just time consuming and error prone. My recommendation: If you can, deploy radiant to a subdomain instead of a subdirectory. For example to dictionary.yourdomain.com instead of yourdomain.com/ dictionary -- swartz On Nov 26, 12:35 am, Ahn Byungmo <b-...@cec-ltd.co.jp> wrote: > Hello~ I' m trying to deploy my radiant web application with use sub-directory > > just like below > > localhost/ > localhost/dictionary > > so i've tried to search how to deploy in sub directory in everywhere > then i got some clues about change config/enviroment.rb > to add below line > config.action_controller.relative_url_root = "/dictionary" > > and it's simply works nevertheless it's not change about public path, it's > not that story > I mean under public path's image files or css files are stil in that path -> > public/image.jpg > > also it has got one more problem that can't be shown files under assets path > so when i access to admim page, every css and image files were not be shown > but still my site was normal, only have problem in admin page > > my env is > ruby - 1.8.7 > radiantcms - 0.9.1 > > anyone can help me please? > Ill thank you in little clue! > > with Best regards!
