From: Kevin <ke...@dr...> - 2005-12-31 06:34:21
|
Evan B wrote: > I take issue with this. The problem with that is that all the config > data gets wiped if the db crashes. As it stands, the only thing you > have to lose is your feed entries, which (to a certain extent) can be > rebuilt rather easily if you have an OPML backup of your feeds. > > e > DB crash, hard drive crash, virtual host goes out of business, what's the difference? Any way you look at it, the data's gone. You should have backups of everything important to you. If you don't, that's your problem. Sorry to be so blunt, but it feels like the wrong approach to be designing the app to compensate for a poorly adminstered database server. With decent abstraction we could offer both config storage methods. (flat file or db table) But for now, I'm leaning toward using the DB. > Katie Bechtold wrote: > >> Kevin commented under Feature Request 1375553 ("customizable >> appearance"): >> >> It wouldn't be a bad idea to have the ability to store >> global config options in the db. Then, config.php could be >> pared down to just the db connection info and table names. >> >> I think that's a good idea. Is that something you're working on, >> Kevin? Once we have a page for user configuration, I could work on >> input and storage of user login info for digest authentication. And >> we could move forward with allowing the user to customize fofredux's >> appearance. >> >> >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel |