Hi Folks,<div><br></div><div>I could use some help on adding a tool to the cloud version of Galaxy. The Cloud startup process creates, among other things, /mnt/galaxyTools/galaxy-central which has tools_conf.xml, and subdir tools etc. This seems not accessible before starting the cloud. I assume I need to add my tool into the structure as per a local Galaxy instance, and then get Galaxy to restart, or re-read it&#39;s config ? Would appreciate some advice there.</div>

<div><br></div><div>Just as background .. I have got a custom proteomics Perl script running ok under a local version of Galaxy on Mac. Added in to tools_conf.xml, tools etc. Made several mods to the Perl to stop any writing to stderr except for fatal show-stopper errors, everyone seems to hit that one, and other small things to make it play better with Galaxy. Also quite familiar with AWS EC2, have been using that for a while.</div>

<div><br></div><div>I have Galaxy Cloudman running well, start/stop extra servers etc. Using the free t1.micro AMI for now, slowish but ok for testing. Or a Spot Instance of m1.large when I&#39;m impatient.</div><div><br>

</div><div>I couldn&#39;t find the answer in a search of Galaxy archives, apologies if it&#39;s there, or obvious in some other way.</div><div><br></div><div>Thanks!<br clear="all"><div><br></div>-- <br>Greg Edwards,<div>

Port Jackson Bioinformatics Consulting.</div><div><a href="mailto:gedwards2@gmail.com" target="_blank">gedwards2@gmail.com</a></div><br>
</div>