3 ms·

The post is against all the people who say stupid things like "mongrel2 doesn't have config files I can put in git" when I've got config files I put in fossil.

by zedshaw 16y ago

The post is against all the people who say stupid things like "mongrel2 doesn't have config files I can put in git" when I've got config files I put in fossil. It's a stupid statement that's just false, and this was the latest reason they gave for saying it was a "real world" concern.

yummyfajitas 16y ago
And just to clarify, I never made this point. The first thing I ever said about this topic was (a direct quote): $ echo '.dump' | sqlite3 mongrel2conf.sqlite > mongrel2conf.human_readable $ git add mongrel2conf.human_readable http://news.ycombinator.com/item?id=1777131 http://news.ycombinator.com/item?id=1777131 I only offered to add the -dbtxt option to mongrel2 when I realized the fundamental problem: people hate learning the sqlite file exists.
- steve19 16y ago
  Is the diff of those sqlite dumps useful? I have had to maintain databases where the dumps were useful and others where there were so many inter-table references that figuring out what the changes did was painful.
  - yummyfajitas 16y ago
    I've only written toy projects in m2 ("look ma, long polling"), so take everything I say with a grain of salt. What I do is manually edit the sqlite dumps. The data flow is one way - edit sqlite dump, import to sqlite, run. I never import and then export the dump. Actually, I don't do any of this. The sqlite file is in .gitignore, and run_my_app.sh does all this. As far as I'm concerned, I just manually config.sql and mongrel2 reads it. If I type ls, I see config.sqlite as well asmy_app.pyc and a few other files I ignore. In principle, I imagine it might be less than useful if you edited your config with some complex sql query. Then again, if you do that, you can't complain the config isn't raw text. Incidentally, why are people downmodding Zed? I don't get it - is his reply to a direct question really harming the conversation here? I'm now thinking I was simply wrong in my proposed solution - hiding the sqlite file from people won't make them any happier.

by zedshaw 16y ago

yummyfajitas 16y ago

And just to clarify, I never made this point. The first thing I ever said about this topic was (a direct quote): $ echo '.dump' | sqlite3 mongrel2conf.sqlite > mongrel2conf.human_readable $ git add mongrel2conf.human_readable http://news.ycombinator.com/item?id=1777131 http://news.ycombinator.com/item?id=1777131 I only offered to add the -dbtxt option to mongrel2 when I realized the fundamental problem: people hate learning the sqlite file exists.

steve19 16y ago
Is the diff of those sqlite dumps useful? I have had to maintain databases where the dumps were useful and others where there were so many inter-table references that figuring out what the changes did was painful.
- yummyfajitas 16y ago
  I've only written toy projects in m2 ("look ma, long polling"), so take everything I say with a grain of salt. What I do is manually edit the sqlite dumps. The data flow is one way - edit sqlite dump, import to sqlite, run. I never import and then export the dump. Actually, I don't do any of this. The sqlite file is in .gitignore, and run_my_app.sh does all this. As far as I'm concerned, I just manually config.sql and mongrel2 reads it. If I type ls, I see config.sqlite as well asmy_app.pyc and a few other files I ignore. In principle, I imagine it might be less than useful if you edited your config with some complex sql query. Then again, if you do that, you can't complain the config isn't raw text. Incidentally, why are people downmodding Zed? I don't get it - is his reply to a direct question really harming the conversation here? I'm now thinking I was simply wrong in my proposed solution - hiding the sqlite file from people won't make them any happier.