1. configure -default to create a new LocalSite? .cfg, as though the user hit save on the file path guesses
2. configure -enable PluginName?
3. configure -set name value set any known parameter
4. configure -install PluginName? (install or upgrade, using the extension installer - may be more difficult dur to file ownerships..)
5. configure -test checks the config for validity

the first 2 will make the buildTWikiRelease script much simpler.

-- TWiki:Main/SvenDowideit - 19 Aug 2007

 

 

Interesting idea. My one concern would be running configure as a non-web user. The advantage of always using the web interface is that the user is always "right".

-- TWiki:Main.CrawfordCurrie - 21 Aug 2007

 

agreed - this is partially to address the need to create canned cfg's to make the unit tests run, the build system go &c

especially as I've found myself writing code to do this at least 6-7 times this year, i figure one configure to rule them all would be apropriate.

-- TWiki:Main.SvenDowideit - 21 Aug 2007

fix a minor crash when running from cmdline

-- SvenDowideit - 10 May 2011