Here'shttp://groups.google.com/group/rubyonrails-core/browse_thread/thread/4d43c1fa2485f3e3an
interesting thread addressing a potential vulnerability of sites for
which the site developer fails or forgets to change the 'secret key' in
enviroment.rb. They discuss various remedies, including
session key, and
you shouldn't be running Radiant on a live site in that mode anyway.
Sean
Dan and Norine Simpson wrote:
Here's
http://groups.google.com/group/rubyonrails-core/browse_thread/thread/4d43c1fa2485f3e3
an
interesting thread addressing a potential vulnerability of sites
As for Dan and Norine Simpson's message about needing to specify the
directory for a new instance, I don't recall ever not needing to do that.
The rails command has the same requirement. But perhaps I'm misunderstanding
something.
I don't recall having to do that in the past. I only noted
A brand new installation seems to require specifying the name of the
directory for your installation. So, for example:
-bash-3.00$ radiant
Usage: /home/danorine/ruby/bin/radiant /path/to/radiant/app [options]
Options:
-r, --ruby=path Path to the Ruby binary of your choice
Oh dear. Is cat skinning a requested feature of Radiant? Surely that can
be moved to an extension, along with pelting, flaying, and tanning.
You know, for the sake of the children and vegetarians.
On Mon, Jul 21, 2008 at 4:35 PM, Chris Parrish
[EMAIL PROTECTED] wrote:
I can get PNGs to
Hi Jan,
Try this: Open an ssh terminal. Run the following commands and post the
results.
gem env
cd /path/to/radiant
ruby dispatch.fcgi
You can also run ruby with the debug flag on (-d) but i find that even a
working installation generates a lot of spurious complaints.
Good luck!
On Sat,
Thanks, Josh!
On Tue, May 27, 2008 at 3:16 PM, Josh French [EMAIL PROTECTED] wrote:
does Radiant plays well with rails
plugins? I recall something about differences in the file structures
creating incompatibilities.
Dan,
Rails plugins (or the majority of them) work just fine under
