Galaxy is actually stored separately from the AMI, but the revision you'll get by default right now is:

changeset:   5757:963e73d40e24
date:        Wed Jun 29 13:27:01 2011 -0400

You can use hg directly to update galaxy, or you can use this component of the admin panel to do it:

Just click update galaxy, and it will update all the way to tip for you.  You also have the option of specifying a particular revision, if you'd like.

And lastly, yes, you will want to persist these changes to have them available the next time you run your cluster.

On Jan 12, 2012, at 3:46 PM, Greg Edwards wrote:

Hi,

Still experimenting with Galaxy and Cloudman on AWS EC2.

The latest galaxy AMI is described as 861460482541/galaxy-cloudman-2011-03-22.

How up to date is that Galaxy rev ? 

Should I use hg to update it before running, or saving as a customised Cloud AMI ?

Thanks. 

-- 
Greg Edwards,
Port Jackson Bioinformatics Consulting.
gedwards2@gmail.com

___________________________________________________________
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using "reply all" in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

 http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

 http://lists.bx.psu.edu/