Jason Tackaberry wrote: > I want to see as much work out-of-the-box as possible. I think this > process should create a freevo user, and drop a couple startup scripts > in /etc/init.d. Because after yum install, in order to solve #4, I > think it should work like this: > > service freevo-webserver start > > On first-run it would find a free port (starting at 8080 say). Now the > web service should be the primary interface to configure freevo. > > I think a web front-end for configuration is probably the best bet. > There are only five possibilities I can think of for this: > > I. Hand editing config files only > II. gtk (or whatever) based GUI > III. Text-based UI > IV. UI within freevo itself for configuration > V. Web-based UI
I had the same idea. That is one reason for kaa.config. Freevo does not use it right now, but with kaa.config freevo has a. a structured list of config objects, sorted in groups b. a description of the config objects c. a way to detect config errors (type checking) d. write support of the config So (i) is still possible and it should be possible to write (ii) or (iii) independed of freevo. For (v) we need more work, but it is on my todo list, but first the webserver needs to be working again. And (iv) is possible for some options. Dischi -- NOTICE: -- THE ELEVATORS WILL BE OUT OF ORDER TODAY -- (The nearest working elevator is in the building across the street.)
pgpcrBL9EAg4Z.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
