> Here are a couple thoughts from a devil's advocate perspective: > > Question: what if our "joomla" site gets hacked some how and vandalized? > How easy is it to roll back changes and restore a site after it's been > damaged? With our current system it's real easy ... I just rerun the web > site rsync command and yell at the ISP to fix the security hole. If the > problem is all contained within our mysql database and user managment > system, then that could be harder to deal with. These are things we'll > have to explore, but I assume there is a way to backup the entire site off > line and restore it later if there is a problem? We supposedly have that > capability with our phpbb forum, but the restore side of this has never > been tested. Security and recoverability and fixability is something we > need to consider if we were to make an official move from a simple system > to a far more complex system. Joomla is a mature system and these topics have all been addressed. At least technically. We need someone with the knowledge how to perform these tasks, though. > > 2. Simplicity versus complexity. For a long time I displayed a "powered by > vi" banner on my personal home page. That was somewhat intended in humor, > but it was also at least half true. My site was actually powered by a > combination of vi + emacs. You may continue to use vi + emacs to edit the template. And for the content, you may use the mysql command line client and to a 'insert into jos_content blah blah blah;' if you hate the gui ;-) > You probably already know this about me, but I do often view the latest > fads and the latest hype with a certain amount of skepticism. I am I going > to get massively flamed in 2 years when "froombla" is released and it's way > better than joombla and we aren't using it? :-) That will happen anyway - no matter if we stick to the current site or move to Joomla, typo3, xoops, [enter_your_favourite_cms_here]. No escape. > Have any joombla sites > crashed and burned because someone had a weak password and their account > was hacked? Or because there was some security hole in the code? And if a > mysql database gets corrupted or damaged for some reason, how hard is the > repair job? First question: Definitely yes. Second question: If they had a backup, other than the avsim guys: it's easy.
My conclusion is: Having the technique, the CMS, is just premise #1. A complex system needs one or better two operators for the housekeeping. They need a certain skill and a good bunch of spare time to do the job. I am not talking about creating a flashy template or writing some content. It is the dirty all day work: removing spam, (un)locking users, resetting passwords, granting/revoking rights, etc. Just have a look at the countless hours Gijs and is spending on the wiki and you know what I mean. But if we can perform the task of setting up and operating a CMS, it will be a great improvement for flightgear.org. Torsten ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
