Fun With Radiant

How to enable Travis CI for an extension

John Muhl — Fri, 06 Jan 2012 15:01:12 GMT

This information is also available on the wiki where it will receive updates as needed.

Travis CI is a flexible and easy to use continuous integration server; see the Getting Started page for more details. The flexibility means that there are any number of ways to setup and test your extensions. Here is one way.

First you need to add a .travis.yml file to the root of your repository.

rvm:
  - 1.8.7
  - 1.9.2
  - 1.9.3

before_script: "./spec/ci/before_script"

script: "./spec/ci/script"

env:
  - RADIANT_VERSION=0.9.1 DB=mysql
  - RADIANT_VERSION=0.9.1 DB=postgres
  - RADIANT_VERSION=1.0.0 DB=mysql
  - RADIANT_VERSION=1.0.0 DB=postgres

notifications:
  recipients:
    - you@example.com

The rvm array shows the Ruby versions you want to test against; since Radiant 1.0 supports the three latest Ruby releases your extension should too. Likewise the env array list Radiant version/database combinations to test against; the Radiant version can be any tagged version of Radiant.

Next up we need to create the before_script referenced above. The before_script is run before your tests and sets up a complete Radiant environment within which your tests will be run.

cd ~
git clone git://github.com/radiant/radiant.git
cd ~/radiant
if [[ $RADIANT_VERSION != "master" ]]
then
  git checkout -b $RADIANT_VERSION $RADIANT_VERSION
fi
cp -r ~/builds/*/YOUR_REPOSITORY_NAME vendor/extensions/YOUR_EXTENSION_NAME
gem install bundler --pre
bundle install

case $DB in
  "mysql" )
    mysql -e 'create database radiant_test;'
    cp spec/ci/database.mysql.yml config/database.yml;;
  "postgres" )
    psql -c 'create database radiant_test;' -U postgres
    cp spec/ci/database.postgresql.yml config/database.yml;;
esac

bundle exec rake db:migrate
bundle exec rake db:migrate:extensions

Replace YOUR_REPOSITORY_NAME and YOUR_EXTENSION_NAME in the before_script with the actual name of your repo and extension; e.g. radiant-sheets-extension and sheets respectively. Don’t forget to make this script executable before committing it to your repository.

Finally we need to create the script file. This is the script that actually executes your tests.

cd ~/radiant
bundle exec rake spec:extensions EXT=YOUR_EXTENSION_NAME

Again you need to replace YOUR_EXTENSION_NAME with the real thing and make the script executable.

All that’s left to do is login to Travis, enable the commit-hook for you repository and push. Head over to http://travis-ci.org/ and click the “Sign in with GitHub” link. Once you’ve authorized through GitHub visit your profile page on Travis, find the extension to enable and flick the switch to on.

Now you’re ready to commit and push the .travis.yml, before_script and script files and let Travis handle the rest. If you want to know more about all the options you have with Travis the documentation is very good. You can see an example of this setup in action on the Sheets extension or check out what it looks like to have your specs run by Travis by visiting the Travis page for Sheets. Once setup Travis will run your tests after every commit unless you add [ci skip] to the commit message (which is good practice when pushing documentation or other commits that don’t affect functionality).

Radiant 1.0.0 Release Candidate 4

Jim Gay — Fri, 06 Jan 2012 03:09:10 GMT

Radiant 1.0 is almost here. Release Candidate 4 has been pushed to rubygems.

Thank you to everyone that’s been helping out with this release.

If you’ve got a site or extension, please begin testing against this release. As always, report any problems or feature requests at https://github.com/radiant/radiant/issues

gem install radiant --pre and you’re on you way!

The installation instructions are at the wiki with a link to a gist where I’ve been recording a step by step process for upgrading from Radiant 0.9.1

Additionally, John Muhl has been doing a fantastic effort in documenting the installation from scratch for Ubuntu Mac OS X and we’ll be updating instructions for Windows and Gentoo.

There’s a lot thats new, too much to cover here, so look for more blog posts about the new features.

Radiant 1.0.0 Release Candidate 2

Jim Gay — Wed, 01 Jun 2011 05:53:29 GMT

Thank you to everyone that’s been helping out with this release.

If you’ve got a site or extension, please begin testing against this release. As always, report any problems or feature requests at https://github.com/radiant/radiant/issues

gem install radiant --pre and you’re on you way!

Benny Degezelle is on the Radiant Core Team

Jim Gay — Wed, 25 May 2011 03:00:41 GMT

Please reach out to Benny Degezelle and say “thanks.”

Benny Degezelle is a member of the Radiant Core Team. He’s been a long time supporter of Radiant and has created or contributed to many extensions and has even more hot code at github.com/jomz

Send him some “thank you”s on Twitter at @jomz

Radiant 1.0.0 Release Candidate 1

Jim Gay — Tue, 24 May 2011 07:05:07 GMT

Announcing the first release candidate of Radiant 1.0.0.

The final 1.0 release will be the last on Rails 2. After that we’ll be focusing on moving forward with the rails framework.

There are a couple of changes that are worth mentioning, but see the CHANGELOG for the full details. What are some big changes?

You can manage multiple page fields
You have a default asset manager based on paperclipped
You have a default stylesheet and javascript manager with support for Sass
Radiant has moved to Rails 2.3.11

If you are an extension developer, begin upgrading now. The official release of 1.0 is just around the corner.

As always we welcome your feedback and contributions.

Download & Install

You can download the gem here http://github.com/radiant/radiant/downloads

Install it with the gem command:

$ gem install radiant --prerelease

This will install the gem as ‘radiant-1.0.0.rc1’.

How to Upgrade an Existing Project or Site

1. Update the Radiant assets from in your project:

rake radiant:update

2. Migrate the database:

rake production db:migrate

3. Restart the web server

RadiantCasts episode 25 - Radiant As A Blog - Part 3 - Adding Tags

Cristi Duma — Thu, 18 Nov 2010 08:08:00 GMT

In part three of Radiant As A Blog, you'll see how to use and configure the Tags Extension, to add tagging functionality to Radiant.

Content

Installing and configuring the Tags extension;
Adding tags to a post;
Tag clouds and tag lists;
Related posts;

Resources

Radiant Tags Extension - github repository
Radiant Taggable Extension - github repository
Github repository for episode 25

Cristi Duma is a software engineer at Aissac.

Radiant 0.7.2 - Engravings Retro Release (bugfix)

Andrew vonderLuft — Mon, 15 Nov 2010 08:23:14 GMT

Radiant 0.7.2 Engravings is a simple bugfix release, recommended for developers using 0.7.1, who write or run specs.

We have discovered a very remote edge case when running specs, that if the default Cache directory, ResponseCache.defaults[:directory], is explicitly set to blank or nil, the cache directory is interpreted as ‘/’ and thus clearing the cache in your spec triggers the execution of `rm -rf ‘/’`.

Upgrading an existing project/site from 0.7.x

1. Update the Radiant gem:

% gem install radiant -v 0.7.2

2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.7.2”.

3. Restart the server

RadiantCasts episode 24 - Radiant As A Blog - Part 2 - Adding Comments

Cristi Duma — Thu, 04 Nov 2010 05:15:45 GMT

In part two of Radiant As A Blog, you'll see how to use and configure the Comments Extension, to add blog-like comment functionality to Radiant.

Content

Installing the Comments extension;
Basic usage;
Configuration and customization;

Resources

Radiant Comments Extension - github repository
Github repository for episode 24

Cristi Duma is a software engineer at Aissac.

Paths and URLs

Jim Gay — Wed, 03 Nov 2010 04:51:06 GMT

At the heart of Radiant’s Page model has been the find_by_url method.

It takes a path, and finds the proper bit of content to display. I wrote a detailed explanation of how find_by_url works on my blog.

In the future things like this will be changing. Our url and find_by_url methods and their ilk haven’t truly had anything to do with URLs, but with paths. So we’re fixing that. The next release will refer to “path” where “url” used to be but don’t worry, everything will work just as you expected if use the current url methods.

To get the same behavior, you’ll need to use methods like path or find_by_path since that’s what you’re really after. This commit shows some of the changes that are upcoming. For now, everything will work the same. We’ve aliased the methods for the next release of Radiant so that your page’s url and path are the same. But they won’t be the same in subsequent releases.

A url method will return an actual URL such as http://radiantcms.org/blog instead of just /blog. We have an open issue related to this at github which describes the same thinking laid out here.

If you’re running on edge, start your switch now.

Design first philosophy

Jim Gay — Tue, 28 Sep 2010 03:43:12 GMT

Radiant has always taken the design first approach to the user interface. Did you know that we use a really simple and easy to use prototyping project at http://github.com/radiant/radiant-prototype

It’s where we work out ideas for the application before we need to put much effort into the code. This has been done for a long time, but most people don’t know about it. We’ve decided to make it easier for everyone to see and understand. Take a look at it in action at http://prototype.radiantcms.org/

Any time there is a push to the main prototype project, it’ll show up at the prototype site.