I think that's a great idea. You may be interested in checking out Björn's
Galaxy Docker image
https://github.com/bgruening/docker-recipes/tree/master/galaxy which is
very similar to what you're describing. A few other testing frameworks,
like Galaxy bootstrap https://github.com/jmchilton/galaxy-bootstrap, use
there own caching mechanism too.
On Mon, Jul 21, 2014 at 12:51 PM, Eric Rasche <rasche.e...@yandex.ru> wrote:
> Currently the checkout options consist of hg clones, and archives that
> mercurial produces.
> Having pulled or cloned galaxy a few times lately, I'm wondering if anyone
> would have a use for a once-run galaxy instance in an archive? I.e., I'd
> clone, run once to grab eggs and do the db migration, then re-tar result
> and store online. Might cut down on build/test times for those who are
> using travis or other CIs. Thoughts/opinions?
> Eric Rasche
> Programmer II
> Center for Phage Technology
> Texas A&M Univesity
> College Station, TX 77843
> Ph: 4046922048 <http://tel:4046922048>
> 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:
> To search Galaxy mailing lists use the unified search at:
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:
To search Galaxy mailing lists use the unified search at: