3 ms·
The canonical version of the server configuration doesn't play nice with version control, and so staff has to work with a facsimile and hope that nobody makes o
by groaner 16y ago
The canonical version of the server configuration doesn't play nice with version control, and so staff has to work with a facsimile and hope that nobody makes out-of-process changes.
You claim that this is a social problem, and I claim that the solution to the social problem is to have a well-defined process.
Even if the canonical configuration is under version control, that still does not prevent anyone from making out-of-process changes.
- yummyfajitas 16y agoI completely agree with you. Let me clarify: the social problem is that everyone is whining about how they are forced to know that config.sqlite exists. They even need to remember this while writing their "run_my_webapp.sh" script. I'm proposing a command line option which hides the `m2sh load -config examples/config/sample.conf` step from the user, and stores the config.sqlite file somewhere other than the working directory. The sole goal is to make people STFU about the config format.
- Avshalom 16y agoPart of the idea behind mongrel2 and using sqlite is that there isn't supposed to be a canon config script/format thingy. Baking m2sh into mongrel2 so you can pass it in with a flag canonizes it. I admit that right now it does seem to be the de facto standard but that's at least partly because the m2 community is small enough that Zed is still important in it so the tools he ships are the tools people use. In the event that m2 takes over the world though an -m2sh (or similar) option is going to be criticized as obsolete bloat that no one needs because every one uses the M2ConfigDeploy.py library.