2009

2008

2007

Dragonfly prefs

▁ aug 26 2007

For those of you who have been running off trunk for the last couple revisions, it’d probably be useful to clear out your prefs for Dragonfly now that we have working code back in SVN as of this afternoon. If you haven’t - this blog post probably doesn’t apply to you. :)

Basically, you’ll just need to delete your /preferences/dragonfly file in the store. Instructions are provided with this entry, so if you’re reading this post via a Planet, you’ll need to click to ‘read more’, if you need to read them.

First, you’ll need to telnet into the store. Provided Bongo is running, use telnet localhost 689 or bongo-storetool telnet (thanks Alex) to connect. Once you’ve done that, enter the following commands into the telnet session (each command should return a response of some kind after you’ve typed it and hit enter):

AUTH USER [user] [pass]
STORE [user]
DELETE /preferences/dragonfly
QUIT

NP: Junior Jack - Life

← Previous: I can do Inkscape!  //  Next: Scissors, paper... →

comments

Alex Hudson, 3 years ago:

bongo-storetool telnet is also good :)

Luis Matos, 3 years ago:

How about … versioning the prefs.

adding a tag on top of the prefs file (i don’t know it’s format) so that the prefs can be validated and changed based on their version.

basically, if this is pref V1.0, then the versions var has to be 1.

if version == 0 erase prefs.file from store

this could be done and it would be useful in future upgrades on the prefs conf file and the way to manage that.

if we are using bongo with about 10 users (or just 3), imagine the trouble.

just my two cents … maybe invalid.

Alex, 3 years ago:

Luis, at the moment we do actually have a versioning parameter in the preferences file, and we probably will end chekcing up against that with future versions.

However, people running M1 and M2 have no/empty preferences files, so upgrading/clearing it out isn’t really an issue. The only reason it would be is as I mentioned - for those people running on trunk who, if they’ve been using some of the previous revisions of the preference code, might have some funny stuff still stuck there.

powered by
∝