couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Smith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1867) Plugins
Date Sat, 17 Aug 2013 16:34:48 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742967#comment-13742967
] 

Jason Smith commented on COUCHDB-1867:
--------------------------------------

Sure. As long as I can enable/disable plugins at start time, without having to change the
files installed on the filesystem, I am happy.

Bob (or anybody), how familiar are you with official or at least traditional Erlang software
deployment? Do you have any thoughts about using the Erlang releases, or upgrade packages,
or appup files for plugin development? Basically I would like to cut with the grain of whatever
practices are already done or recommended by the Erlang community.

For example, suppose a plugin author built a plugin as an Erlang application, then cut a release,
and somehow fed that to CouchDB. Does that strike anybody as a plausible avenue?
                
> Plugins
> -------
>
>                 Key: COUCHDB-1867
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1867
>             Project: CouchDB
>          Issue Type: New Feature
>            Reporter: Jan Lehnardt
>            Assignee: Jan Lehnardt
>            Priority: Minor
>
> It should be easy to install CouchDB plugins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message