[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-promo
Subject:    [kde-promo] Re: Enterprise site
From:       Thomas Thym <ungethym () mevin ! net>
Date:       2011-05-10 11:31:48
Message-ID: 201105101331.48982.ungethym () mevin ! net
[Download RAW message or body]

On Tuesday 10 May 2011 11:21:13 wrote Ben Cooksley:
> On Tue, May 10, 2011 at 9:03 PM, Lukas <1lukas1@gmail.com> wrote:
> > > 
> > > KDE has selected Drupal as it's CMS option in general, and (from a
> > > Sysadmin point of view anyway) is much easier to adminster, manage and
> > > keep updated in comparison to Wordpress (which has to have an instance
> > > per site, in comparison to Drupal which can have a single shared
> > > instance, with modules which can also be shared).
> > 
> > Well actually WP has this feature for a long time
> > http://en.wikipedia.org/wiki/WordPress#Multi-blogging :)
> 
> It looks like it does, but it has a key deficiency in that it can't
> handle more than one domain. ie. it could handle sites under
> *.kde.org, but not kdenews.org or behindkde.org. It also can't handle
> aliases (like news.kde.org & dot.kde.org)
> 
> Further, all the sites use the same database access credentials, so if
> you manage to breach one site at the sql layer, you breach them all.
> Drupal allows completely independent MySQL settings for each site, and
> is fully domain flexible.
> 
> Regards,
> Ben

From my point of view the decision is made and there is no alternative (at the \
moment). It does not make sense to change the CMS now. Besides that I want to \
underline that I trust the sysadmins 100% and stand completely behind their \
decisions. They do the work, they choose. And what I see it woks out very well. \
Thanks for that.

Best regards,
Thomas
 
_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on \
or temporarily stop your subscription.


[prev in list] [next in list] [prev in thread] [next in thread]