Will XOOPS be a good fit with my website?

The server is running Solaris 8 (sparc processor) and runs the iPlanet web server. My site receives about 400,000 page views per day, about 50,000 page views per day to the home page. The server is "behind" an Akamai caching solution and therefore is not "highly stressed".


My website is a big target for hackers. I receive about 2,000 attempts per month of people trying to find a backdoor into my system. That is why I only run static pages now, because I am scared to open up a hole on my system by installing XOOPS and PHP/mysql.

Is there a way to make the CMS only accessible to the webmaster (who VPNs to the web server)?

Can XOOPS run in "non-php" mode and just generate static HTML pages??

Please advise! Thanks!

Quote:
No, it will kill host

With that sort of load I expect you'd have a dedicated server? I think what you want can be done with Xoops, but only with careful consideration and planning. It would be impossible for anyone here to say if using XOOPS would or wouldn't present a security risk, as apart from XOOPS itself you also have to consider PHP, MySQL and your webserver. There is no "non-PHP mode" as such, and it would take some work to get your system so that it only serves static content to your users with XOOPS operating as the CMS in be backend. Don't know what your requirements or website entails, but I would almost say you are better off with a fully customised application built to your needs than traying to mould something like XOOPS to do the job. That's just my initial impression tough and I only rank myself as an advanced XOOPS user at best. Guys in the core design team such as Mith or Skalpa would be better suited to answer such a question.