sklassen commented on issue #27: vm.args is now editable -- enabling clusters; snap set works for name and cookie URL: https://github.com/apache/couchdb-pkg/pull/27#issuecomment-431544119 Hi @wohali I have little experience with either travis or docker so I'm a little lost on what is needed for CI testing. My knowledge of snapcraft, too, rudimentary, but I am happy to support the snap. I'll continue to track and reply to issues, if that helps. I think that snapcraft is a useful asset for the CouchDB community. Docker is a nifty tool, but it is an extra layer between the application and the os; snap runs directly on the os -- as a high-performance database should. The ease of which to switch snap versions without overwriting configuration files is useful too. Of your number point above, number 3, "Dispense with the build entirely and just have the snap install the couchdb package from our bintray repo." looks like the best choice. I too was uncomfortable with the size of the snaps. This solves a lot of issues and reduces the yaml file by two-thirds. It's a pity, however, to lose the ability to build snapcraft from either github or tar ball. Maybe I'll create a snapcraft-source.yaml and snapcraft-package.yaml and link to the second one. That way we don't lose the community knowledge of the first method. I'll hunt about for examples. With the couchdb configure command. There is a --disable-fauxton and --disable-docs; could there also be a --disable-couchjs. This simplifies the build and you can drop in the couchjs binary afterwards. I removed my username from the configuration file. It shouldn't have been there -- it slipped in there with another change. I'll also unpublish my couchdb-sklassen snap once we have an official release. Of the issues #13 (native snapd configutation) My pull request solves directly #17 (error creating view) Is a problem I too had. This hass solved in the latest snapd. Prior snap version didn't have permission to run 'nice' when building views, @mhall119 fixed this; a workaround was to run snap in devmode #19 Looks to be a nodejs version issue on build. I didn't encounter this with 2.2.0. I think this can be closed.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
