[
https://issues.apache.org/jira/browse/COUCHDB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726790#comment-13726790
]
Bob Ippolito commented on COUCHDB-1867:
---------------------------------------
As far as plugin installation goes, I think we should probably just put them in
prefix/lib/couchdb/plugins/ (same location as the built-in support now) and
have the convention to be to make this writeable by the couchdb user. /tmp is
obviously not a real solution :)
For distro-installed plugins, there could be another directory. Perhaps the
boot script could allow you to specify more than one plugin directory for this
purpose? I don't have a lot of insight into why linux distro packagers do what
they do and how they want to do it.
I think the "plugin blacklist" support could use a lot of work too. The way
that grep is done is definitely not the right way to do it, and it should
probably be in a file instead of (or in addition to) an undocumented
environment variable. To be honest I'd rather put as much of this configuration
stuff into Erlang and out of shell scripts as possible, but that would be a
separate issue than this.
> 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
