There is nothing special on the instance of Galaxy deployed through CloudMan, so any changes performed to the configuration of Galaxy should be tested the same way they would be tested if they were installed on a local system. That said, if there are system dependencies that need to be satisfied for some of the functionality to work, the update is more complicated because it would, most likely, involve creation of a new AMI. Especially if the mentioned�functionality�is not working on the default instance of CloudMan, we should work out the issue and release a new CloudMan AMI that fixes the underlying problem. I'll test the functionality you mentioned on a new instance of Galaxy CloudMan and help you resolving the issues.

Enis

On Fri, Mar 11, 2011 at 5:32 PM, Isabelle Phan <isabelle.phan@seattlebiomed.org> wrote:

I am at step 2 of Galaxy CloudMan deployment.
"Now, manipulate Galaxy as desired."

How do I test that my updates are working before proceeding to step 3?

I assumed I could just type 'run.sh'. This starts Galaxy but:
- fasta files do not display in the middle pane
- png images generated by e.g. boxplot do not display in the middle pane
- saving images does not work (get empty file)

I need to know how people are customizing their cloud instance of galaxy. If it is NOT possible to test modifications in the usual way PLEASE would somebody simply confirm?

I really would appreciate a response.

Isabelle
--
Isabelle Phan, DPhil
Seattle Biomedical Research Institute
+1(206)256 7113

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. �To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

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