search

jdswinbank / Comet

A complete VOEvent transport system
http://comet.transientskp.org/
BSD 2-Clause "Simplified" License
23 stars 9 forks source link

More flexible plugin installation location #62

Closed jdswinbank closed 4 years ago

jdswinbank commented 5 years ago

Dumping plugins into Comet/comet/plugins isn't convenient, especially if you're (e.g.) installing Comet using pip into a Docker container. Please come up with a flexible way of enabling the user to specify the plugin location.

jdswinbank commented 5 years ago

One nice possibility might be a namespace package, although, more work is necessary to see if it can actually be made to work.

JulienPeloton commented 4 years ago

Hi John,

63 introduced the COMET_PLUGINPATH environment variable to deal with plugins in a easier way from an user point of view. The published documentation does not mention it yet, so should I consider it as still experimental?

In any case, I'm planning to write plugins so I can report on its use if it is useful.

jdswinbank commented 4 years ago

Hi @JulienPeloton —

This feature hasn't yet made it into a released version of Comet, so from that point of view it is still experimental. However, it is available (and documented) on the master branch, if you are willing to try running that.

As far as I'm aware, master is reasonably stable: I intend to release it as Comet 4.0.0 when I get chance (although that might not be for a while yet). However, be warned that it does include a substantial overhaul of the command line interface — see the release notes for details.

jdswinbank commented 4 years ago

I think this issue was closed by #63

JulienPeloton commented 4 years ago

Thanks @jdswinbank for the clarification and the pointer to the release notes!