<distilled from IRC chat> A separate password file as described above, but can only be updated thus;
# couchdb --set-password admin Password: foo Password updated. # Whether this password is written to a separate file or to a future _config database is immaterial, but separate file is proposed for the first implementation. In the case of the latter, the issue of locking yourself out is raised, so we propose adding; # couchdb --admin-party Apache CouchDB <version> (LogLevel=info) is starting. Apache CouchDB has started in admin party mode! Time to be scared! [info] [<0.31.0>] Apache CouchDB has started on http://127.0.0.1:5984/ # B. On 17 August 2011 15:16, Noah Slater <nsla...@apache.org> wrote: > > On 17 Aug 2011, at 15:07, Jason Smith wrote: > >> The .ini file that edits itself. There are probably some servers out >> there which do that, but as you know, sysadmins expect /etc files to >> stay put! Many use CVS to manage them, as you noted. >> >> Hence, I like the generated.ini idea because as a sysadmin, during >> peacetime (couch is running fine) it is just an opaque file blob I >> need to back up. During wartime (couch is crashed/misconfigured), I >> can dig into it with emacs and troubleshoot. > > Gotcha. :) >
