4 ms·
I'm aiming for operational understanding of the data model used over being able to directly work with the config file. If it's a .ini (or other conf) usually y
by zedshaw 16y ago
I'm aiming for operational understanding of the data model used over being able to directly work with the config file. If it's a .ini (or other conf) usually you have no idea how the config maps to internal data structures. It's a mystery why some stanzas in nginx work on FastCGI but not Proxies for example.
With a sqlite3 based "config file" you'll be able to use real, turing complete languages to configure it, create control pannels, distribute the config reliably, and you can run .schema to figure out how it's structured.
It's also incredibly reliable and has many great features for this kind of thing.
- viraptor 16y agoIsn't the nginx's problem solvable with consistent implementation and complete documentation too? I guess running some programming script isn't that bad to configure the server - but right now, people do a lot of basic operations on configs via shell scripting which do the deployment. Using bash/sh to interact with sqlite doesn't sound very inviting.
- zedshaw 16y agoPossibly, it's a littler early to tell, but I'm sure I'll make it easy to use from the shell. Could even be possible to create converters from other config file formats to the Mongrel2 data model as well.