Actually, both of these help. I'm putting a boto.conf file into /mnt/galaxy/galaxy-app and setting the BOTO_PATH environment variable from the python script that needs it, so it will work in dev (non-clusterman setup) and production. Jim On Fri, Apr 25, 2014 at 11:20 AM, Dannon Baker <dannon.baker@gmail.com>wrote:

Ahh, sorry about that, I misread the bit about it actually needing to be in the user's directory. You could use a worker_post_start_script to configure things like this (creating/copying .boto at boot from the shared space in the script). See https://wiki.galaxyproject.org/CloudMan/UserData for how to specify that in your UserData.

-Dannon

On Fri, Apr 25, 2014 at 11:13 AM, Dannon Baker <dannon.baker@gmail.com>wrote:

...

Hi Jim,

/mnt/galaxy is shared via NFS with all cluster workers -- this (or a subdirectory) should work for you.

-Dannon

On Fri, Apr 25, 2014 at 10:56 AM, Jim McCusker < jmccusker@5amsolutions.com> wrote:

...

Hi all,

I need to add a .boto file to the user that galaxy jobs get exec'ed as on cloudman nodes. I thought it would copy over what the galaxy server has in its home directory, but that doesn't seem to happen. How can I get things like my .boto file to migrate over to new cloudman nodes when they are spun up?

Thanks, Jim

___________________________________________________________ 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/

To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/