Hi all,
I've recently updated my local instance of Galaxy from bitbucket to
git. It seems to work fine. No error when we run galaxy.
But I've been tried to cleanup datasets and when I ran this command :
python scripts/cleanup_datasets/cleanup_datasets_Redirection.py
universe_wsgi.ini -d 0 -1 -r $
You might consider a secure login for users affiliated to other instutitutions
than your lab as well. Then you can implement a redirection to a set of IdPs
with delegated permissions to authenticate users against your LDAP but also
against many other LDAPs.
Feel free to come up with questions
Hello,
I have a very big problem with a module I've been tried to install for galaxy.
I've install Crate with this command
pip install Crate
But when i verify in sites-packages, and in a python prompt, this
module is named with a "c" and not a "C", so Galaxy cannot restart
Please help me .
J
This usually means there is an error of some kind - perhaps a missing
tool. Sorry it is not more transparent - I'd check the Galaxy logs for
an error message if possible or open the JavaScript console of your
web browser
(https://developers.google.com/web/tools/chrome-devtools/debug/console/?hl=en
Hi,
installing tool dependency package_pybamtools_0_0_2 as well
as package_pybamparser_0_0_1 cause below mansion errors.
Following the tool_dependencies.xml file:
hg clone -r
ba0341816b15fff5e0a554658d6579a60e1b12b1
https://bitbucket.org/dan/pybamtools pyBamTools
$INSTALL_DIR/lib/python
expor
Is this something inside the application or external to it? If it is
external to the application - I'd probably just target the database
directly (Postgres or MySQL). The internals of Galaxy use sqlalchemy
for the most part (http://www.sqlalchemy.org/). I've done a lot with
the database but I've ne
Any follow up on this? I have never seen this - but it would be worth
specifying a full absolute path for conda_prefix in galaxy.ini and see
if that fixes it. If it does - I can open a PR that makes sure this
variable is always an absolute path.
On Thu, Sep 1, 2016 at 11:37 PM, Léo Biscassi wrote
Hope you made some progress on this - my guess based on the stack
trace is that you have some subtle difference related to a parameter
named ``uncol`` in some tool that is contained within both instances.
On Fri, Jun 10, 2016 at 2:14 PM, Tony Schreiner
wrote:
> We have 2 galaxy instances running
Hello Zipho,
Per your request I have reviewed the linked issues and created a
list of things I think can be done that are relatively easy to improve
the current situation here
https://github.com/galaxyproject/galaxy/issues/2980#issuecomment-250777589.
There are a lot bigger things that need to b
In general we discourage this - but there is some conversation about
this here - at least as it pertains to the instance URL and API key:
http://dev.list.galaxyproject.org/find-UUID-of-current-history-in-tool-XML-wrapper-td4667113.html
The workflow is more tricky - if you are sure the job is goin
10 matches
Mail list logo
