Radiant 0.6 RC2

Read all about it:

http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/


John L.
http://wisheartdesign.com

Great!

How you upgrade from RC1?

Regards,
Erik.

John W. Long wrote:

Read all about it:

http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/


Erik van Oosten

Erik van Oosten wrote:

How do you upgrade from RC1?

Uninstall the old gem and install the new one. Then run:

rake radiant:update


John L.
http://wiseheartdesign.com

John W. Long wrote:

Read all about it:

http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/

I should also add that RC2 includes recent changes in Mental that allow
you to run script/generate in instance mode:

script/generate extension AssetManager


John L.
http://wiseheartdesign.com

Instance mode is the mode where the whole Radiant code is copied into
your project?
If I understand correctly, instance mode is required to develop
extensions (which I intend to to). Or are there other means?

I am sorry, its all a bit vague to me. Perhaps I have not yet seen the
right documentation. Or perhaps there are just too many options :slight_smile:

What would be the appropriate way to operate when you want to develop an
extension which will be available for others, potentially through svn,
but definitely through some other way (gem?)? (Perhaps important: I
still did not have time to finish my svn setup.)

I wrote a camping application to manage a virtual e-mail domain with
postfix (redirects only). I would like to convert it to a Radiant
extension.

Regards,
Erik.

John W. Long wrote:

script/generate extension AssetManager


John L.
http://wiseheartdesign.com


Erik van Oosten

John W. Long wrote:

Read all about it:

http://radiantcms.org/blog/2007/03/08/radiant-0-6-release-candidate-2/

Woo hoo! Keep up the good work! Go team!

Any way for me to learn just what those “cool new features that only
people brave enough to check Mental” are exactly?

I try to keep tabs on what people are working on via this list but I
suspect there’s more than I know about.

-Chris

Erik van Oosten wrote:

Instance mode is the mode where the whole Radiant code is copied into
your project?

No. Application mode is where you are running straight off the source.

If I understand correctly, instance mode is required to develop
extensions (which I intend to to). Or are there other means?

No. Instance mode is not required to develop extensions.

I am sorry, its all a bit vague to me. Perhaps I have not yet seen the
right documentation. Or perhaps there are just too many options :slight_smile:

The documentation for it is a bit poor. Instance mode is what you get
when you install radiant from a gem and run:

% radiant /path/to/my/project

To create the default structure for your site. The main benefit to
instance mode is that the source code for Radiant can reside in the gem
but the Radiant project contains all of your configuration. This makes
it easy to upgrade. In the future the upgrade process will be as simple
as:

  1. Install the new gem:

    % gem update radiant

  2. Update your config/environment.rb so that it uses the latest gem.

  3. Update your radiant project:

    % rake radiant:update

  4. Run any migrations:

    % rake production db:migrate

The other way of installing Radiant is known as “Application” mode.
Application mode is what you get when you install Radiant by extracting
the source into your project directory. If you install Radiant this way
you will be on your own when it comes to upgrading your version of
Radiant. Because of this instance mode is the recommended way of
installing Radiant.

What would be the appropriate way to operate when you want to develop an
extension which will be available for others, potentially through svn,
but definitely through some other way (gem?)? (Perhaps important: I
still did not have time to finish my svn setup.)

You can develop extensions in instance mode or application mode. To get
started just run the following command from your project root:

% script/generate MyExtensionName


John L.
http://wiseheartdesign.com