Store custom variable overrides in database, not in filesystem

Wondering why the custom variables for each virtual site get messed up when a site is moved, I discovered there is an actual INI file for each virtual site, stored in a filesystem directory. Not really what I would expect for something that is a configuration option, and it makes staging sites to/from the production server just one step more tedious (I don't commonly need to migrate anything in the private filesystem).

Any chance the variable overrides could be written to the database, not stored as a file?

I'll take a look at it myself if I get some spare time (yeah, right).