Topic: Grab Refinements to the Kete 1.0 Release Branch
Topic type:
We've had several busy weeks of refining the Kete 1.0 release branch. Now is a good time to update your installation. I'll outline how.
Outdated - Please refer to the newer Upgrade to Kete 1.1 Release
As noted in the blog post where we announced 1.0, by using a "subversion checkout" of the Kete code it's a relatively simply process to update your Kete installation to take advantage of bug fixes and security patches.
Assuming that you have followed the steps for "Simple Installation" in the Installation Guide (you may want to refresh your memory of it before jumping in), here's what you do:
Following the conventions from Preinstall Assumptions topic, we'll go to the "your_app" directory for your Kete application and update the code:
$ cd ~/apps/your_app
$ svn update
$ rake kete:upgrade:add_missing_mime_typesYour Kete codebase is now updated. All that remains is to restart your Kete server and it's supporting Backgroundrb process. We'll do Backgroundrb first and then Mongrel (what answers your web requests).
$ script/backgroundrb stop
$ script/backgroundrb start
$ mongrel_rails cluster::stop
$ mongrel_rails cluster::startThat's it. Your site should now benefit from all the latest work we have done on the 1.0 release branch.
You can repeat the process (the "rake kete:upgrade:add_missing_mime_types" can be skipped next time) regularly to make sure your site is up to date.
If you did the "Optional Best Practices - Managing your Kete application's codebase and deploying it to a production host" see comments below for topic with your exact steps.
was the last to edit Grab Refinements to the Kete 1.0 Release Branch
on Aug 28th, 2008 at 4:25 PM
Discuss This Topic
There are 3 comments in this discussion.
Read and join this discussion
Hello again,
You can find out how to do the update if you followed the Optional Best Practices production deployment part of the Installation Guide here:
http://old.kete.net.nz/documentation/topics/show/151
Cheers,
Walter
Posted on March 13th, 2008 at 4:18 AM
As mentioned in http://old.kete.net.nz/blog/topics/show/175-kete-moves-code-repository-and-issue-tracker-to-new-homes, we have moved our code repository and issue tracker to new services.
Rather the previously mentioned feeds (that are now discontinued), please use the following:
for tickets - feed://kete.lighthouseapp.com/events.atom
and for code commits - feed://github.com/feeds/kete/commits/kete/master
Enjoy,
Walter
Posted on August 2nd, 2008 at 2:06 AM
Walter McGinnis
said Track when there are bug fixes
If you want to know when there are bug fixes or security upgrades added to the Kete 1.0 branch, the easiest way is to subscribe to this RSS feed:
feed://development.kete.net.nz/rss/changesets
This feed also includes changesets that are added to trunk, too. So if you see a notification of bug fix that it looks like you should grab, it is a good idea that they are relevant to the Kete 1.0 branch by visiting here:
http://development.kete.net.nz/kete/repository/changesets
and then clicking the changeset in question for details.
Cheers,
Walter