Hi,
We ran into a problem if galaxy is running behind multiple reverse proxies.
Galaxy assumes that the X-Forwarded-Host header only contains a single host
to which it redirects, but apache will append comma-separated components to
it if it already exists, which is the case of multiple reverse pro
Hi everybody,
In our lab, we are trying to connect our Galaxy instance to a Windows 7
64 bits server, in order to executes programs that need to be run within
Windows. However we have a problem concerning the size of the input that
is uploaded to the Windows server, it doesn't accept inputs wi
Hi galaxy-dev members
Recently we're trying to setup the galaxy server in a production mode.
Everything seems to be ok
but when I tried to upload a file it shows error message like this
Failed: Not found(404)
I found one thread in galaxy-dev fourn about this one
It says that it's because of
Hi,
I want to integrate Galaxy with another system. When I log in this system, then
click a link jump to Galaxy, this user has already logged into Galaxy.
Now, I can use api to create a user at the same time in this system and Galaxy,
but how to use api to log in Galaxy?_
I made the erroneous assumption that if I put my own admin user API key into
the galaxy configuration master_api_key field, it would accept that and run all
the api functions that needed a key connected to a user. It took fair bit of
debugging to realize that the master_api_key field chops off
On Tue, Nov 18, 2014 at 5:51 PM, Nate Coraor wrote:
> Peter,
>
> Unless you've made modifications to Galaxy that depend on external
> libraries, switching to a virtualenv for the server itself should be
> pretty safe. Tools themselves can still run without using the/any
> virtualenv, if desired.
>
Peter,
Unless you've made modifications to Galaxy that depend on external
libraries, switching to a virtualenv for the server itself should be
pretty safe. Tools themselves can still run without using the/any
virtualenv, if desired.
--nate
On Tue, Nov 18, 2014 at 8:24 AM, Peter Cock wrote:
> On
On Tue, Nov 18, 2014 at 1:24 PM, Peter Cock wrote:
> On Nov 18, 2014 7:26 AM, "John Chilton" wrote:
>>
>> I will admit to not actually understanding Galaxy's dependency management
>> but I think virtualenv is exactly the advice people who do understand it
>> give
>> http://dev.list.galaxyproject.
On Nov 18, 2014 7:26 AM, "John Chilton" wrote:
>
> I will admit to not actually understanding Galaxy's dependency management
> but I think virtualenv is exactly the advice people who do understand it
> give
> http://dev.list.galaxyproject.org/Local-installation-problem-td4662627.html.
> It is a wi
Oops forgot to cc the list.
On Nov 18, 2014 7:26 AM, "John Chilton" wrote:
> I will admit to not actually understanding Galaxy's dependency management
> but I think virtualenv is exactly the advice people who do understand it
> give
> http://dev.list.galaxyproject.org/Local-installation-problem-t
On Mon, Nov 17, 2014 at 7:23 PM, John Chilton wrote:
> Ummm... I think it is that the VM started shipping with an
> incompatible paramkio.
>
> [...]
>
> Anyway - planemo's TravisCI integration tests Galaxy in a virtualenv
> and it works fine [...]
That's a useful workaround, but a virtualenv is n
11 matches
Mail list logo