Instance mode set-up

Ruby Apps Radiant CMS
1

Anyone know where to find the definitive guide for installing in
instance mode? And does anybody use the Google group anymore or is the
mailing list the preferred location for questions? Seems that the docs
and how-to’s for radiant are a little disorganized. Nonetheless, I
really like the radiant platform but am confused about the ‘what’ and
‘how’ of instance mode.

-Luke

2

Instance mode is what you get when you install according to the most
recent instructions:

http://radiantcms.org/blog/archives/2007/04/24/radiant-0-6-lapidary-release/

I believe the Google group was just a mirror for the primary mailing
list. John has debated moving the list over to Google completely, but
with 500+ subscribers, that’s hard to do efficiently without losing a
bunch of people.

Sean

3

Anybody else having a problem with the radiant command not installing
all of the typical rails dirs? When I run ‘radiant path/to/project’,
I’m not getting the ‘app’, ‘lib’, and other dirs. I’m running winxp with
rails123, ruby185, rubygems091.

Any help is appreciated.

-Luke

4

Thanks, I figured as much until I found this post on the mailing list:
http://lists.radiantcms.org/pipermail/radiant/2007-June/005238.html

It seems to say that the radiant command does the same thing as the
rails command.

So, what I’m doing now is running ‘rails my_app’, then running the
radiant install instructions, although now I’m getting an error during
rake db:bootstrap that the users table doesn’t exist.

One of those days, everything I try is blowing up.

-Luke

5

Luke,

Sorry, that’s a feature, not a bug! That’s what we mean by instance
mode – the minimum of necessary files is placed in your chosen
directory and the rest is loaded from the gem or from vendor/radiant.
It’s especially nice for shared hosting or multi-site environments where
you don’t want to install all of the files for each new site.

Sean

6

On 6/8/07, Luke W. [email protected] wrote:

Anyone know where to find the definitive guide for installing in
instance mode? And does anybody use the Google group anymore or is the
mailing list the preferred location for questions? Seems that the docs
and how-to’s for radiant are a little disorganized. Nonetheless, I
really like the radiant platform but am confused about the ‘what’ and
‘how’ of instance mode.

-Luke

I have a tip for instance mode: if you happen to install certain
extensions on all of your Radiant instances, like I do with the Copy
Move extension, install them in your global radiant extension
directory instead of your instance dir.

For me on Debian, it’s in
/usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/vendor/extensions

Of course, in case of a new Radiant Gem version, you will have to move
your extensions to the new dir, ie. radiant-0.6.2/vendor/extensions

Question: will this still work if I freeze one instance to edge? Will
the frozen Radiant still be looking in the global vendor/extensions
dir?

7

I have a tip for instance mode: if you happen to install certain
extensions on all of your Radiant instances, like I do with the Copy
Move extension, install them in your global radiant extension
directory instead of your instance dir.

Great tip!

For me on Debian, it’s in
/usr/local/lib/ruby/gems/1.8/gems/radiant-0.6.1/vendor/extensions

Of course, in case of a new Radiant Gem version, you will have to move
your extensions to the new dir, ie. radiant-0.6.2/vendor/extensions

Question: will this still work if I freeze one instance to edge? Will
the frozen Radiant still be looking in the global vendor/extensions
dir?

No, it will not. RADIANT_ROOT gets set to vendor/radiant if it exists
and ignores the gem. However, if you froze the gem instead, the
extensions should get copied over.

Sean

8

On 6/9/07, Sean C. [email protected] wrote:

Question: will this still work if I freeze one instance to edge? Will
the frozen Radiant still be looking in the global vendor/extensions
dir?

No, it will not. RADIANT_ROOT gets set to vendor/radiant if it exists
and ignores the gem. However, if you froze the gem instead, the
extensions should get copied over.

Sean

And how do I freeze the gem instead of freezing the Radiant instance?

Thanks!

J.

9

rake radiant:freeze:gems

Sean

10

On 6/11/07, Sean C. [email protected] wrote:

rake radiant:freeze:gems

Sean

Simple as that :slight_smile:

Thank you Sean.

J.

11

On 6/11/07, Jonathan Métillon [email protected] wrote:

On 6/11/07, Sean C. [email protected] wrote:

rake radiant:freeze:gems

Sean

Simple as that :slight_smile:

Thank you Sean.

J.

rake radiant:freeze:gems replaces rake radiant:freeze:edge or should
be invoked after?

12

On 6/12/07, Jonathan Métillon [email protected] wrote:

rake radiant:freeze:gems replaces rake radiant:freeze:edge or should
be invoked after?

I just tried and it looks like freeze:gems first delete vendor/radiant
then copy the gems.

So, if I freeze to my current gems, then I’m not running edge and
page_attachments will break?

Thanks.

J.

13

rake -T will also show you all of the available tasks.

Sean

14

That is correct. We should have 0.6.2 soon though… John said in a
week or two last time we talked.

Sean

15

Luke W. wrote:

Thanks, I figured as much until I found this post on the mailing list:
http://lists.radiantcms.org/pipermail/radiant/2007-June/005238.html

It seems to say that the radiant command does the same thing as the
rails command.

So, what I’m doing now is running ‘rails my_app’, then running the
radiant install instructions, although now I’m getting an error during
rake db:bootstrap that the users table doesn’t exist.

Do not use the rails command and then the radiant command! All you need
is the radiant command.

–
John L.
http://wiseheartdesign.com