RE: [Firebird-website] (no subject)

[Pavel C. <pc...@at...>]

Hi,

I agree with Helen that we should put first things first :) So we 
should first decide about requirements to the site, next to its 
structure etc. But we can also summarize the facts, to set up 
margins for decisions.

So, few facts:

We have private MySQL database + PHP4 at SourceForge. I don't 
know the limits for database size (should we ask SF staff ?). We 
have cca 100MB web space here (more could be negotiated). 
Everyone in project can access that space through SSH/SCP (it's 
a great plus). The Apache server is not overloaded (of course, it 
have a peaks, IMHO mostly due maintenance) and average 
response time is acceptable if not very good (and should be in the 
future, because VA Linux care about this and upgrade hw when 
necessary). Also connectivity to the NET is very good (check for 
yourself the SF doc page about that :). I'm not sure about backups, 
so we have to do that ourselves for web space and for database too 
(web is in CVS, so it's in safe if someone keep backup of daily 
CVS tarballs, BTW did that someone ? I've few whole cvs tarballs, 
but I don't do that regularly. It's general admin issue!!!). I do 
database dump + backup every two weeks or so. We can use CGI, 
but I'm not sure about the policy. I guess that CGI should be at 
least reviewed by SF staff, because they care about security. 
Actually, I didn't investigate about CGI. We CAN'T set up another 
database (FB) or environment (we should have standard Linux 
tools, like pearl, python, sending mail etc. but I don't know the 
details), nor reach any service outside the SF domain from our web 
(php), so plans about database at our own server are not doable. 
SF staff is very careful about security (and that's good). We can 
also get the VHOST, i.e. our own domain for web site. All in all, the 
quality of service at SourceForge is superb (to some extent :).

It's a fact, that our web could be anywhere and from some angle, it 
could be better if it would be, but... The host'll have to:

- good connectivity to NET, guaranteed uptime (TBF)
- secure access for many people (web team) and admin tools at 
their disposal
- regular backups
- tools to run the site (php, zope, whatever)

Some notes about tools and infrastructure: It should (or shall?) be 
open source, so we can tweak them and adapt them to our needs 
as their change. And yes, it would be nice if we would be able to 
eat our own dog food (FB).

To Nick Josipovic: I'm not against your proposal (it's great), but 
take to consideration what I wrote above.

Best regards
-- Pavel