[kepler-dev] Kepler and loading modules from external location

[barseghian at nceas.ucsb.edu]

Hi Michal,
A slight correction to Matt's response: they're downloaded into 
~/KeplerData/kepler.modules/. You can see an example of how this 
works by using Tools=>Modules Manager to download reporting-2.3.
Important to note is kepler.modules/build-area/.

As Matt describes, technically it should work right now, if a user 
puts their modules in this location and edits kepler.modules/build-area/ 
txt files by hand. A cleaner more user-friendly solution would require
more work, 
probably to the module-manager, module-manager-gui, and build-area.

Derik

On Thu, 29 Mar 2012 08:54:38 -0800, Matt Jones <jones at nceas.ucsb.edu>
wrote:
> Michael --
> 
> Modules that are downloaded by the module manager are installed in your
> home directory, under $HOME//KeplerData/modules -- so you should be able
to
> use that location.  Of course, you also need to modify various
> configuration files to load the module into your current suite -- really
> this should be done through the Module Manager.  Currently Kepler only
> knows how to manage modules that have been released in the standard way
(
>
https://kepler-project.org/developers/teams/build/documentation/publishing-steps)
> -- you would have to find a workaround to allow the Module Manager to
use
> locally obtained modules instead of obtaining them over the network.
> 
> Matt
> 
> On Thu, Mar 29, 2012 at 1:40 AM, Michal Owsiak
> <michalo at man.poznan.pl>wrote:
> 
>> Hello Kepler team,
>>
>> I have question related to module location.
>>
>> At the moment, we are using Kepler in such configuration that all
modules
>> are stored inside Kepler directory.
>>
>> We are looking for a solution, where we have central Kepler
installation
>> (lets say /opt/kepler), but at the same time, users can have their own
>> module (most probably this will be the same module name for each user,
>> e.g.
>> user-module-2.4) in $HOME directory.
>>
>> Users are expected to put their own extensions into this module.
>>
>> Question is:
>>
>> does Kepler provide any means of putting module outside main Kepler
>> directory structure?
>>
>> If not, what would be the effort to introduce this kind of feature and
>> what parts of Kepler would be affected by this change?
>>
>> Thanks in advance for your suggestions.
>>
>> Cheers
>>
>> Michal
>>
>> --
>> Michal Owsiak <michal.owsiak at man.poznan.pl>
>>
>> Institute of Bioorganic Chemistry PAS
>> Poznan Supercomputing and Networking Center
>> Noskowskiego 12/14, 61-704 Poznan, POLAND
>>
>> http://www.man.poznan.pl
>> ______________________________**_________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>>
http://lists.nceas.ucsb.edu/**kepler/mailman/listinfo/**kepler-dev<http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev>
>>