There's not an ideal solution for your situation. My suggestion:
(a) set up a cloud instance with your tools + a Page and use the
"share-an-instance" feature so that others can access your data, tools,
histories, and page in a single place ( http://wiki.g2.bx.psu.edu/Admin/Cloud );
(b) put your tools into the tool shed for easy access (
(c) replicate the page + as many of the histories as possible on our public
server, with a note about how to get going with either (i) tools from the tool
shed or (ii) on the cloud.
We're working to make public server-cloud access more easy, so there may be
something on the horizon that could smooth (c)(ii) out.
On Apr 18, 2012, at 5:02 PM, Todd Oakley wrote:
> Jeremy -
> Thanks so much for your helpful responses.
> One problem that i didn't mention with implementing your suggestions is
> that the histories I want to post contain mainly new tools that my lab
> developed for phylogenetics using transcriptome data. Therefore, the public
> instance does not have most of the tools in the history (we will put these on
> the tool shed as soon as we can). In addition, the analyses are VERY
> computationally intensive, including assembly and Maximum Likelihood
> analyses, and therefore probably are not suitable for re-running on the
> public Galaxy instance. (This is also a reason why I cannot make my local
> galaxy instance public - it exposes too many tools that could bog down the
> host computer).
> Additional suggestions most welcome…
> On Apr 17, 2012, at 6:33 PM, Jeremy Goecks wrote:
>> Hi Todd,
>>> [Not sure if this is better suited to galaxy-dev or -user, so I'm sending
>>> to both].
>> galaxy-user is most appropriate for this question because it related to
>> usage of Galaxy; galaxy-dev is for local installation and tool development
>>> My question is - can I create a Galaxy 'Published Page' from my local
>>> Galaxy instance/histories, and then transfer that page to the main Galaxy
>> Not currently, though this is in our long-term plan.
>>> The reason is that I cannot make my local Galaxy instance public, as I am
>>> using a campus resource to host our galaxy. If this is possible, how can I
>>> do that? If not, any other ideas?
>> It is possible to move datasets and workflows relatively easily between
>> instances, so I'd recommend that:
>> (a) you move your data and workflows to our public instance;
>> (b) rerun your analyses on the public instance to create the required;
>> (c) create and host the Page on our public instance.
>> You can be assured that we will maintain our public server over the coming
>> years and your Page will remain available and have a stable URL.
>>> Also, are there any tutorials/pages on how to create Published Pages in
>>> Galaxy in the first place?
>> Not yet, though the idea is for the Page editor to be self explanatory.
>> Here's how to get started with Pages:
>> (a) from User menu, go to Saved Pages;
>> (b) create a Page;
>> (c) edit the Page using the Web-based editor; there are menus for inserting
>> embedded datasets, workflows, histories, and visualizations as well as
>> performing standard word-processing operations.
>> Let us know if you have problems/questions and we'll start a guide for
>> creating Pages.
>> 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:
>> To manage your subscriptions to this and other Galaxy lists,
>> please use the interface at:
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:
To manage your subscriptions to this and other Galaxy lists,
please use the interface at: