You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/11/08 01:17:38 UTC

[GitHub] sklassen commented on issue #38: local.ini sourced from tree on installation

sklassen commented on issue #38: local.ini sourced from tree on installation
URL: https://github.com/apache/couchdb-pkg/pull/38#issuecomment-436837724
 
 
   > I thought we agreed that your configure hook would put its `10-<section>.ini` files in `etc/default.d`. This still seems to be putting them in `local.d`. Which is it?
   
   snapcraft.yaml is writing to /snap/couchdb/current/rel/couchdb/etc/default.d once and only with one file couchdb.ini and only specifying the data and index directory which is specific to a ubuntu snap installation. For this reason /etc/default.d is mounted read-only.
   
   the install and config hooks are user-generated changes and sit in  /var/snap/couchdb/current/etc/local.d on the writtable /var mount
   
   /snap/couchdb-sklassen/current/rel/couchdb/etc/default.ini and /var/snap/couchdb-sklassen/current/etc/local.ini are both per usually, but the former read-only and the latter writable. 
   
   I think this is consistent with the /snap/couchdb/current/rel/couchdb/etc/default.d/README. "snap set" are user changes and should be in local.d.
   
   I'll add a number to default.d/couchdb.ini so that it looks like local.d 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services