Radiant runs fine on cedar. Here's a site Im currently building on the
cedar stack :
But there are a few gotcha's with the Gemfile, you'll also need to add
a Procfile and delete the config.ru (breaks compass for some reason I
Here's a gist :
Locally I generally run without the production group :
$ bundle install --without production
I haven't included any extensions in the Gemfile but if you want to
use Heroku's memcache add-on with Radiant then a simple extension I
created seems to do the trick, just add it to the production group :
gem "radiant-heroku_dalli-extension", "~> 1.0.0"
Cedar also removed the Varnish caching layer but I've been getting
pretty good results out of Cloud Flare [https://www.cloudflare.com/]
On Apr 20, 8:22 am, John Moroney <j...@juniork.com> wrote:
> bundle update returns radiant (1.0.1) in the gemfile.lock, which crashes the
> app on heroku
> radiant seems to like only the bamboo stack, if that is important
> I'm currently having a beast of a time getting Radiant to find the js and
> image files. They are not being pointed to correctly in the admin interface,
> though the call is identical to the local copy.
> i would very much like to help in any way I can to simplify the
> radiant/heroku process. My biggest hurdle has always been getting all the
> necessary information in one source, and then getting current information.
> On Apr 19, 2012, at 8:29 AM, Jim Gay wrote:
> > I definitely want to support Heroku easily.
> > Any bug reports or code you can provide would be really helpful.
> > On Thu, Apr 19, 2012 at 1:49 AM, Bruce Davison <bruce.au....@gmail.com>
> > wrote:
> >> I Deploy to Bamboo for Radiant. I only use Cedar for Rails 3. Also Heroku
> >> doesn't use Sqlite3 it uses Postgresql. If you are using taps to push your
> >> db it creates a Postgresql database
> >> Hope that helps
> >> --
> >> Bruce Davison
> >> Sent with Sparrow
> >> On Thursday, 19 April 2012 at 11:52 AM, John Moroney wrote:
> >> It was that I deployed to the cedar stack, mostly. On cedar, it would not
> >> resolve sqlite3, saying it was either missing or needed a sqlite3.h. I also
> >> had to change the gemfile.lock from radiant (1.0.1) to radiant (1.0.0) for
> >> the app to fire. I'm still showing some unresolved dependencies which I'm
> >> trying to run down, and now my admin/content is css-less.
> >> And only on Heroku.
> >> Locally? Brilliant as ever.
> >> For the record, thanks for Radiant. I've been using it since 2006-2007.
> >> John Moroney
> >> On Apr 17, 2012, at 9:01 PM, john wrote:
> >> what exactly is the problem with heroku?
> >> On Tuesday, April 17, 2012 8:52:03 PM UTC-5, John Moroney wrote:
> >> I usually deploy to Heroku, but can someone suggest a more Radiant-friendly
> >> server? It's the deployment which seems to be the bottleneck, even after
> >> the
> >> experience of many installs.
> >> Heroku has many advantages, one of which is being free for micro-scale
> >> sites
> >> and blogs. Are there low-priced, Rails-friendly servers that are still in
> >> the Ruby/Rails community?
> > --
> > Write intention revealing code #=>http://www.clean-ruby.com
> > Jim Gay
> > Saturn Flyer LLC
> > 571-403-0338