Re: MRFC: Midgard site startup and configuration.
Torben Nehmer <[email protected]>
| Newsgroups | gmane.comp.web.midgard.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, - --Piotras wrote on 2006-02-07 11:36: >>> I am not any component developer but: Two sites I initilized without M-T >>> are not working anymore and frankly speaking I have no time or will to >>> debug what happened. However M-T is slow I vote for M-T. Reason is very >>> simple. I know that M-T based sites are going to work as expected. >> >> You think so, ok. I have nearly a dozen of examples where current M-T broke >> more things, than it fixed. It is purely a matter of perspective. >> >> We need a site management system, but not something like current M-T. > > OK, I will correct myself ( probably I am the only one midcom *user* on this > dev list ). As a user I need something like M-T. It doesn't matter for me > what's under the hood. That is for sure. See my first mail, it outlines the way it should work in my eyes. It'll give people like you a full GUI to manage the site and people like me (using the custom sections) ways to actually influence and fine-tune startup. >>> $some_midcom_site->port $some_midcom_site->prefix >>> $some_midcom_site->whatever >>> >>> Is *much* more readable than another set of huge set of arrays. >> >> Leading to a table which needs to be extended with each and every >> configuration option I add to MidCOM. Right now, we already have literally >> dozens of such options (around 50 I guess) part of which are system-wide, >> part of it site-specific. Some options are even complex types, not simple >> ports or prefixes. > > I do not think you would like to have 500 configuration options. It doesn't > have to be db related. I was only pointing to arrays' hell ( probably I am > the only one midcom *user* on this dev list ). The array isn't trivial, I agree here. But normally you don't have to work with that array in any way. Right now, if you cannot use m-t for whatever reason, site startup is rather trivial, the only thing really needs specification in a standard environment is the root topic GUID. I grant that the array isn't exactly user-friendly, but I fully trust that you can populate a global array with a single guid until we have a more powerful system. Most other configuration options which are relevant are in the system wide config file in /etc anyway (which can be auto-generated using autoconf.php as I outlined somewhere in my blog). I have never said setting up MidCOM is trivial (as Midgard setup is anything from trivial still). But we're getting better. Live long and Prosper! Torben Nehmer - -- Torben Nehmer, Guenzburg, Bavaria, Germany http://www.nathan-syntronics.de, mailto:[email protected] PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD6HqFJPh4Kn6d5FYRAlhtAJ9BYw9W4TTtyP4aYUp9W/lqVFzqmACgsno5 NSkCVJ9o6z8KRZl/5opXTxE= =938E -----END PGP SIGNATURE-----