librelist archives

Re: [mongrel2] Config files - migrations and replication

From:

Zed A. Shaw

Date:

2010-10-10 @ 08:53

On Sun, Oct 10, 2010 at 09:32:02AM +0100, Zeke Rondel wrote:
> The idea is to be able to replicate changes to your config using
> migrations and to be able to replicate those changes to all your servers
> in one shot, or roll them back, etc.

People do all of this with sqlite3 all the time.  You don't need:

> Then, to get it there is a better DBMS. Couchdb[1] uses a Multi-Version
> Concurrency Control (MVCC) model for read operations. It is a peer-based
> distributed database system, it allows for users and servers to access
> and update the same shared data while disconnected and then
> bi-directionally replicate those changes later.

Well nothing really prevents you from doing this. Few folks talked about
redis, couch, pretty much any flavor of the month NoSQL database comes
up.  As I showed you can do .ini files, python, lua, C, hell anything.

Really, if you wanted you could do this today.  Just write some simple
little thing that pulls configs and changes from a couchdb and makes
sqlite out of it.  Next step would be gutting the config.c stuff and
loading right out of couchdb.

We won't support it, but the code's very simple and doing stuff like
this is super easy. Go ahead and try.

One warning though, proposing that the project adopt couchdb is a
non-starter.  We want people to be up and running and productive quick.
We just ripped out Python because it was too hard for people to install.
Yes, Python was too hard to install.  There's no way in hell CouchDB and
Erlang and whatever else crazy ass libraries you need are going to be
easier than Python for our users.

So, try out your idea, the code's there.  But consider it an experiment
and not something we'll push out to people as their first install
experience.

-- 
Zed A. Shaw
http://zedshaw.com/

I'd a similar idea about use a different configuration system --than
flat files-- for servers although it didn't like too in the the [Go
mailing list][1].

Now, knowing that it has been already implemented and that it has real
advantages then I'm motivated to get it. Thanks!

I had not considered the problems of installation on CouchDB but at
least Ubuntu comes with it pre-installed and Ubuntu server will be my
server. Anyway I'll have to see which technology I'm going to use for
storing, CouchDB, SQLite3, or Tokyo Cabinet


[1]:
http://groups.google.com/group/golang-nuts/browse_thread/thread/c81ccd22b866577a/

On Sun, 10 Oct 2010 01:53 -0700, "Zed A. Shaw" <zedshaw@zedshaw.com>
wrote:
> One warning though, proposing that the project adopt couchdb is a
> non-starter.  We want people to be up and running and productive quick.
> We just ripped out Python because it was too hard for people to install.
> Yes, Python was too hard to install.  There's no way in hell CouchDB and
> Erlang and whatever else crazy ass libraries you need are going to be
> easier than Python for our users.
> 
> So, try out your idea, the code's there.  But consider it an experiment
> and not something we'll push out to people as their first install
> experience.

-- 
http://www.fastmail.fm - Faster than the air-speed velocity of an
                          unladen european swallow