I'm not sure it's usable in today's world. The Rails version in master is
pinned at 2.3.x, and Ruby 1.9, neither of which are really viable without a lot
of patching for CVEs and such. There was a branch about 6 years ago trying to
move to Rails 4. But here is is 2019 and we have Rails 6. Not
Thank you so much for all your hard work. This is excellent news, and I can't
wait to see what happens next.
Walter
On Feb 28, 2012, at 10:46 AM, Jim Gay wrote:
I'm proud to be able to release 1.0:
http://radiantcms.org/download/
Many good things have gone into this long-awaited
On Sep 12, 2011, at 3:29 PM, James Martens wrote:
Hello!
I've been banging my head against the wall on this one for a bit. I'm
intermediate with my rails skills but this is my first radiant site. I
am trying to deploy to a Radiant 1.0 rc2 to a server hosted at
slicehost. I am hoping a kindly,
On Sep 12, 2011, at 7:40 PM, john wrote:
On Monday, September 12, 2011 6:23:04 PM UTC-5, James Martens wrote:
Is there any way to see better output from passenger? I know it
produces nice looking 500 errors to help trace things, and normally
that is how I solve these issues, but I can't seem to
On Aug 4, 2011, at 8:58 AM, Phillip Oertel wrote:
Hi Radiant team,
I want to evaluate a few Rails-based CMSes soon. Since I still find
it hard to decide on which Rails CMS to use, I want to blog the
evaluation as well, so others have it easier.
I definitely want to include Radiant, but
If I start a project today with the current stable (0.9.x) version,
what would my upgrade path look like when 1.0 is released for real? In
Rails 3, I would just update my bundle, but with 2.3.x, it's not
nearly that clean in my limited experience. Can anyone pat me on the
shoulder and say
