Jon Roberts said the following on 11/09/2009 11:52 AM: > There's an extensive guide at > http://wiki.dreamhost.com/index.php/Ruby_on_Rails > > Deployment of Rails apps seems to be a little different everywhere you > go, so for evaluating CMSs, you should probably just run it locally. I > can vouch that Radiant does indeed run on Dreamhost, though.
Indeed. I'm running five Radiant sites on Dreamhost and will be adding more before the year is out. Recall this is a SHARED environment - unless you are willing to pay them extra for a dedicated host. So you don't have control over over what is in /usr/lib/ruby/gems. If you are new to RoR then you probably don't know about 'freezing' gems into your application. Hence the instructions on setting up your own gem depository and to put the GEM_PATH to it in your .bash_profile and update your PATH. Non of this is odd to long-time RoR or Linux users. Mind you, the Windows registry is complete bafflement to many Linux users. However as Jon says, there's no need for this I all you are doing is evaluating or prototyping. RoR has its own stack, and I can and do prototype all my sites on my laptop. A small change to the start-up command and my laptop is a server for this application on the LAN. Ta-Dah! So, Brian, perhaps you need to spend a bit more time with the basics of RoR in order to understand the context Radiant is working in. -- People who love sausages, respect the law, and work with IT standards shouldn't watch any of them being made. -- Peter Gutmann _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
