lp:~cmiller/desktopcouch/couchdb-polutes-its-ini

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:desktopcouch

John O'Brien (community): Approve on 2010-02-08

Stuart Langridge (community): Approve on 2010-02-05

Diff: 279 lines (+69/-58)

8 files modified

bin/desktopcouch-service (+8/-3)
bin/desktopcouch-stop (+3/-15)
data/couchdb.tmpl (+2/-2)
desktopcouch/local_files.py (+22/-1)
desktopcouch/records/server_base.py (+7/-1)
desktopcouch/start_local_couchdb.py (+9/-6)
desktopcouch/stop_local_couchdb.py (+17/-28)
desktopcouch/tests/__init__.py (+1/-2)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

130. By Chad Miller on 2010-02-05

Provide a way for old-style bookmarks to be noticed and updated. Try
to parse it the same way as we will later, and if we can't, then make
a new INI file.

129. By Chad Miller on 2010-02-04

When the HTTP status of is not success=200, also raise the body of the
result so that it is easier to debug.

128. By Chad Miller on 2010-02-04

We need to mutate the bookmarks file when couchdb starts, to add the port
number couchdb is listening on. This means we have to know the password.

The only place that the password is guaranteed to be correct between runs
of desktopcouch, without having a new INI file generated and shiny-new, is
the bookmark file itself. Why? Couchdb may, at its bewildering discretion,
mutate its INI file so that the password is hashed and useless to us.
Thus, we can't use the INI file as the source, and it's already in the
bookmarks file.

So, we need to parse the bookmarks file to get the info to update the
bookmarks file. If we're going to do that already when updating the port,
we might as well use the same mechanism when fabricating a new password
when there is no INI file we can use.

127. By Chad Miller on 2010-02-04

Use a context instead of a given PID as parameter to stop_couchdb().

126. By Chad Miller on 2010-02-04

Use the new unified function to shut down couchdb.

125. By Chad Miller on 2010-02-04

Use a context to shut down, if provided. If none given, use the
default context.

124. By Chad Miller on 2010-02-04

Add an easily-parsable container of credential information, because we
will have the resulting file be the only reliable source of existing
credentials, soon.

123. By Chad Miller on 2010-02-04

On init of CouchDatabase, do not fail if the server does not support
teh _changes interface (as UbuntuOne server does not).

122. By Chad Miller on 2010-02-04

Remove dumb shutdown method in desktopcouch module. Move smart shutdown
out of dedicated program to a function.

121. By Eric Casteleijn on 2010-02-02

backported safer update_fields method from server code in a backwards compatible way, fixed tests so they run in lucid (testtools changed so that setUp has to call super's setUp, and same for tearDown), did pedantic cleanup in files I touched