Name: vagrant-galaxy
Owner: Smithsonian Institution
Description: Vagrant launcher for Galaxy
Created: 2013-09-24 16:56:26.0
Updated: 2016-04-29 16:33:19.0
Pushed: 2015-08-24 16:49:35.0
Homepage: null
Size: 223
Language: Shell
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|---|---|
| Andrew Stewart | 2015-01-06 18:50:31.0 | 13 |
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Vagrant launcher for Galaxy (http://galaxyproject.org/)
Note - the easiest way to install Fabric is through pip (or easy_install):
install fabric
clone https://github.com/Smithsonian/vagrant-galaxy.git
vagrant-galaxy
rant up
Point your browser at http://localhost:8080/ after starting up the galaxy server. You can do this via fabric (see below), for convenience, or you can do it manually like so:
rant ssh
/vagrant/galaxy-dist
un.sh --daemon
To start the galaxy server, the included fabric file provides some convenience functions.
vagrant galaxy:start
Likewise, there are options for stopping, restarting, and checking the status of the galaxy server.
vagrant galaxy:stop
vagrant galaxy:restart
vagrant galaxy:status
You can find a full list of available fabric functions by typing the following:
list
Running a toolshed server inside the local VM is a convenient way to run deployment tests for your custom galaxy tools. You can develop your tool (including wrappers, tests, datatypes, dependencies, etc) on the galaxy instance, then upload the package to the toolshed and test installing it back on the galaxy instance.
The syntax is identical to starting the galaxy server:
vagrant toolshed:start
vagrant toolshed:stop
vagrant toolshed:restart
vagrant toolshed:status
For both the galaxy and toolshed servers, the default admin user is vagrant@galaxy.local
Simply create a new user in each webapp with that e-mail address to access the admin menus (or add your own admin user to the config files).
This feature is still in development, but the basic usage is as follows:
vagrant config:OPTION,VALUE