Mental Branch Revision?

Hi Guys,

I’m going to be starting a new site in Radiant (have two others on
0.5.2 already) and wanted to work with mental. Should I just take the
current revision or is there a specific one I should target? Also,
does mental require 1.2/edge?

Cheers,
Marty

The commits tend to be well tested if they affect normal operations, so
it’s
pretty safe to use the current revision. Mental automatically uses Edge
Rails as an svn:external when you checkout.

Sean
p.s. www.kckcc.edu is running the latest revision of mental

Sean C. wrote:

The commits tend to be well tested if they affect normal operations, so
it’s
pretty safe to use the current revision. Mental automatically uses Edge
Rails as an svn:external when you checkout.

Well not quite. It’s using the 1.2 prerelease branch:

http://dev.rubyonrails.org/svn/rails/branches/1-2-pre-release/


John L.
http://wiseheartdesign.com

Daniel,

Could not agree the more. It’s a step many people either skip or give
for granted. Before you do any kind of migration you MUST back up all
the DB, and all the radiant 0.5.x files your site is currently using.
In fact, unless you are tinkering with a testing/dev intall, you need
to make backups before you mess with any file and/or the DB.

Best,
Ruben

Great, so just to confirm before I attempt this. The steps for
upgrading from a 0.5.2 radiant site (installed via gems, no unpack) to
mental is this:

  1. do an svn:co into my site directory (which will put all the
    radiant/rails 1.2 pre release over the old generated radiant rails
    app).

cd my_site
svn co http://dev.radiantcms.org/svn/radiant/branches/mental/radiant/ .

  1. Update the database.yml to correctly point to my existing Radiant db

  2. run rake db:migrate

  3. restart the webserver

  4. login and rock

Right?

Cheers,
Marty

  1. backup the entire site dir + database incase it breaks anything
  1. do an svn:co into my site directory (which will put all the
    radiant/rails 1.2 pre release over the old generated radiant rails
    app).