Hi all!
This is a request for comments regarding the possibility of packaging
Radiant extensions as gems. I am addressing this mostly to those familiar
with Radiant internals. Others are welcome to contribute, of course.
Is it technically possible to load Radiant extesions as gems, in a manner
Istvan,
I am totally for this. Some hurdles we'll have to overcome:
1) Numerous places where files in extensions use a relative path to find
config/environment.rb or other files in the gem. This is especially
relevant to running tests.
2) Resolving inter-extension dependencies so as to avoid
Hi,
I just installed the copy/move extension for a site running radiant 0.8.1
The installation gives the error below. As far as I can tell thoucgh,
the extension works properly.
rake production radiant:extensions:copy_move:install --trace
(in
it looks like the copy_move extension doesn't have an install task try:
rake production radiant:extensions:copy_move:migrate
rake production radiant:extensions:copy_move:update
or just use ./script/extension install copy_move and let it take care
of that for you.
On Thu, Sep 10, 2009 at 9:02
My company is putting together an RFQ for a website project for one of our
clients. We only build Ruby on Rails applications, mostly with Radiant. One
of the requirements for their website is that it be hosted on their Windows
server with IIS. Is this possible? What options are available for
Is there an outstanding reason they can't run apache on windows?
On Sep 10, 2009, at 9:29 AM, Nate Turnage wrote:
My company is putting together an RFQ for a website project for one
of our
clients. We only build Ruby on Rails applications, mostly with
Radiant. One
of the requirements for
On Sep 10, 2009, at 9:47 AM, Brian Loomis wrote:
Is there an outstanding reason they can't run apache on windows?
nginx runs on Windows nowadays too. It's a little less intimidating.
However, I expect they want IIS because of all the management tools,
quick web search reveals you could
The easy answer for this is to use the typical reverse-proxy to mongrel,
thin, or some other Ruby application server. Most web-servers have an
option to do that.
Sean
Nate Turnage wrote:
My company is putting together an RFQ for a website project for one of our
clients. We only build Ruby
You shouldn't have a problem doing it. One of our clients used to be
on IIS and SQL Server with Radiant.
You'll need to purchase isapi_rewrite from
http://www.isapirewrite.com/ or
http://www.helicontech.com/isapi_rewrite/ unless there is some other
way out there to easily do it now. But it was
We just successfully deployed a rails project with the same requirements using
tomcat, IIS, and jruby on rails.
George
--Original Message--
From: Nate Turnage
Sender: radiant-boun...@radiantcms.org
To: Radiant@radiantcms.org
ReplyTo: radiant@radiantcms.org
Subject: [Radiant] Radiant on
On Thu, Sep 10, 2009 at 1:09 AM, Chris
Parrishchris.parrish-forumm...@swankinnovations.com wrote:
I just tried installing radiant 0.8.1 and all went well until I performed a
rake radiant:freeze:gems Now starting mongrel on my development machine
produces the following error:
** Starting
In a similar situation, I have done the reverse: run Apache on port 80
and proxy requests to IIS running on another port. The IIS port is
protected from ouside access by firewall. Rails applications were
running on Mongrel with mod_balancer and managed with the
mongrel_service gem to make the apps
On Thu, Sep 10, 2009 at 12:01 PM, Jim Gay j...@saturnflyer.com wrote:
You shouldn't have a problem doing it. One of our clients used to be
on IIS and SQL Server with Radiant.
You'll need to purchase isapi_rewrite from
http://www.isapirewrite.com/ or
http://www.helicontech.com/isapi_rewrite/
Actually, it looks like an IDE problem (I use RadRails). It would seem
that they are incorrectly inferring the application's working directory
to be the \vendor\radiant\ directory when launching mongrel.
Sorry for the noise.
-Chris
Jim Gay wrote:
On Thu, Sep 10, 2009 at 1:09 AM, Chris
14 matches
Mail list logo
