This document is for an old release of Galaxy. You can alternatively view this page in the latest release if it exists or view the top of the latest release's documentation.
Galaxy Deployment & Administration¶
- Production Environments
- Connecting to a Cluster
- Scaling and Load Balancing
- Galaxy Job Configuration
- Tool Panel Administration
- Dependency Resolvers in Galaxy
- Conda for Tool Dependencies
- 1. How do I enable Conda dependency resolution for Galaxy tools?
- 2. How do Conda dependencies work? Where do things get installed?
- 3. What is required to make use of this? Any specific packages, Galaxy revision, OS version, etc.?
- 4. If I have Conda enabled, what do I need to do to install tools using it? For example, how can I install the latest Trinity? And how will I know the dependencies are installed?
- 5. Can I mix traditional Galaxy packages and Conda packages?
- 6. How do I know what system is being used by a given tool?
- 7. How do I go about specifying Conda dependencies for a tool? All the docs still seem to recommend (or exclusively discuss) the
- 8. During tool installation what if there is no Conda package available for a given requirement? What if the requirement is resolved in a different software than the original wrapper author meant to use?
- 9. Where can I find a list of existing Conda packages that I can point to, so I don’t have to reinvent the wheel for common dependencies?
- 10. How can I create a new Conda package for a dependency?
- 11. Is there a way to convert traditional Tool Shed package recipes that are not yet in a Conda channel?
- 12. What is the recommendation for existing installations? Will I continue to maintain both systems or migrate to the new Conda system eventually?
- 13. What can I do about this placehold error?
- 14. What can I do about this LOCKERROR error?
- 15. What can I do about linking errors?
- 16. What can I do if Conda doesn’t work for me?
- 17. How can I upgrade Conda?
- Framework Dependencies
- Galaxy Reports
- Scripts & Tricks