[Mageia-sysadm] SQL Server
Michael Scherer
misc at zarb.org
Thu Oct 28 19:30:05 CEST 2010
Le jeudi 28 octobre 2010 à 19:02 +0200, nicolas vigier a écrit :
> We will need an SQL server for bugzilla, the packages maintainers
> database, the wiki, the blogs, the mageia.org website (not now, but
> maybe later), sympa mailing lists, transifex, and maybe others tools
> later.
>
> We can use MySQL (or forks), PostreSQL, or both.
Both.
bugzilla use mysql or postgresql
package db ( if we reuse the one of mandriva ) use mysql
wiki not decided yet
blog use wordpress, so mysql ( postgresql is still experimental )
sympa can use both ( or even anything supported by dbi such as
http://search.cpan.org/~rehsack/DBD-AnyData-0.110/lib/DBD/AnyData.pm )
epoll requires postgresql.
our current perl webapp, catdap and mga::mirror requires postgresql.
transifex, being in django support mysql or postgresql
http://docs.djangoproject.com/en/dev/ref/databases/
( or sqlite or firebird )
so we have a majority of database agnostic tools, except a few one that
requires each their own.
Given the activity around mysql and forks, wouldn't it be safer for us
to use postgresql when possible for the moment ?
( not that I think it will change much, IMHO, even if nanar will say me
that postgresql >> mysql )
> One server for everything, or multiple servers.
I would go for :
one postgresql sql server for bugzilla, sympa, epoll transflex, on
alamut or valstar ( since everything will be in local network )
one mysql db for maintainers and maybe others when they appear.
one separated mysql db for web ( blog ) on the next gandi vm ( so there
is no lag )
--
Michael Scherer
More information about the Mageia-sysadm
mailing list