[Radiant] Radiant command without the gem

I remember John mentioning that once you had a full instance of Radiant installed, you could then use the "radiant" command to install further instances, just like using the gem. He said this would be also useful if you had changed the version of Radiant you were using, which is my case, now. Has

Re: [Radiant] 500 status on /admin/

Sean Cribbs wrote: Phil, Make sure that dispatch.fcgi is executable and that the shebang line points directly to your ruby installation and not /usr/bin/env ruby. From a shell, you can type 'which ruby' to find out where ruby is installed. Other than those, make sure that dispatch.fcgi

Re: [Radiant] No entries in log files

Check the log levels for the production mode. The current level may be :warn-MOn 10/3/06, John Tsombakos [EMAIL PROTECTED] wrote:Ok, this is odd.I had switched Radiant to use production mode, and now I'm not seeing any access entries written to any log file - either Apache's log

Re: [Radiant] No entries in log files

On 10/3/06, Mislav Marohnić [EMAIL PROTECTED] wrote: Check the log levels for the production mode. The current level may be :warn -M Ah, true. Missed that one. But would that cause Apache not to make an entry in it's log file? ___ Radiant mailing

Re: [Radiant] Set-Cookie: appearing on page

On 10/2/06, Oliver Baltzer [EMAIL PROTECTED] wrote: Try mod_fastcgi, I have no problem with that and Rails. For me fcgid makes a lot of trouble in a different non-Rails setup and it would not surprise me if it's fcgid that adds those headers at the end of the response. I personally am in the

Re: [Radiant] No entries in log files

Apache always logs - it really doesn't care (know) what production mode you are running your Rails app in.On 10/3/06, John Tsombakos [EMAIL PROTECTED] wrote:On 10/3/06, Mislav Marohnić [EMAIL PROTECTED] wrote: Check the log levels for the production mode. The current level may be :warn -MAh,

Re: [Radiant] Radiant command without the gem

Keith Bingman wrote: I remember John mentioning that once you had a full instance of Radiant installed, you could then use the radiant command to install further instances, just like using the gem. He said this would be also useful if you had changed the version of Radiant you were using,

Re: [Radiant] RoR and Radiant on bluehost?

Kevin Ansfield wrote: Did you code that site? If so how did you do the request a proposal form? Is it through a radiant behaviour or did you code it seperately? I used Matt McCray's radiant_mailer_behavior. Note that his instructions tell you to install radiant_behavior_filters as well, but

Re: [Radiant] RoR and Radiant on bluehost?

Nope; Radiant works great on BlueHost. For example: http://rampartadvisors.com/ -Drew Application error Application failed to start properly... On 10/3/06, Drew Raines [EMAIL PROTECTED] wrote: Kevin Ansfield wrote: Did you code that site? If so how did you do the request a proposal

Re: [Radiant] RoR and Radiant on bluehost?

Alexander Horn wrote: http://rampartadvisors.com/ [...] Application error Application failed to start properly... It worked when I tried it. Unfortunately, Bluehost still uses FastCGI for Rails support, so your request probably caught a rogue process. I didn't claim they were perfect;

[Radiant] Default CSS Layout question

Hello, I am trying to make an adjustment to the default CSS. As I understand it, everything is contained within the page div. I should be able to change the page border:2 px solid black to have a solid border around the page contents. I have tried this several different ways with no

Re: [Radiant] Radiant command without the gem

Thanks John, I was just typing the path incorrectly. That works perfectly. Keith Bingman[EMAIL PROTECTED] On Oct 3, 2006, at 3:56 PM, John W. Long wrote:Keith Bingman wrote: I remember John mentioning that once you had a full instance of Radiant installed, you could then use the "radiant" command