I’m testing the latest galaxy-central (rev 15961:63d901ca0e6e) to try out
dataset collections. First thing I run into is that things don’t seem to run
well when running it on a VM (port forwarded) with nginx. If I click on tools I
get a white screen instead of tool options, and the log show an error from
lib/galaxy/webapps/galaxy/api/tools.py : Checking parameter file failed.
The setup: URL would be galaxydomain.com:3030, which the VM manager forwards to
port 80 on the galaxy VM, which there nginx would forward to port 8080. Now, my
nginx is set up to work with older galaxy versions, I don’t know if that
matters. I haven’t changed any config files at all yet.
When I turn off nginx and serve directly on port 80 (using sudo), things look
like they work. At least the tools look like they should. Has the nginx config
to use changed recently or is this some weird artefact? Anyone else seen it?
Since I’m just goofing around to see how collections work, it is not the end of
the world for me, and I know galaxy-dist is the stable one, but still.
Proteomics systems developer
BILS / Lehtiö lab
Scilifelab Stockholm, Sweden
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: