[axxs-sysadmin] Aotearoa IMC on borg.axxs.org

boud boud at riseup.net
Sat May 26 13:50:56 UTC 2007


hi sebastian,

On Sat, 26 May 2007, Sebastian wrote:

> unfortunately, the whole Drupal situation is not in a state where we can
> switch from Dada on the old server to Drupal on the new. but as the old
> server still has substantial database problems (caused by our site as
> well), i reckon we should get Dada over to the new server better sooner
> than later.

Maybe wait a few more days to be sure, but it seems that the mysql
overload problem was really the persistent connections option.

> i am totally happy to setup everything necessary on the new server on my
> own, given sudo access. recently, i looked at wiki.axxs.org and could
> not see documentation regarding custom setup (yet). is there anything i
> should take care of? the question also is if you trust me enough.
> or perhaps you do not feel ready˙˙for sites to migrate. :)
> my GPG key can be found here:
> http://keys.indymedia.org/cgi-bin/lookup?op=get&search=A9ED38844A1F5E81
>
> presumably, i won't be able to effectively hang around on #axxs much and
> definitely have no time to babysit other projects on the server. an
> occasional fix here and there should be in order, though.

Do you know dada well enough and follow its mailing lists (and i guess
imc-security) to be alerted when exploits are discovered? A bunch of 
dada indymedia sites got cracked some time ago (last 12 months AFAIR)
and some were quite slow to get patched.

Since we seem to have solved the mysql overload problem, IMHO there is
probably no rush to shift to borg if you're not yet ready to
install/migrate to drupal. IMHO it would probably be better to try the
migration from dada at www.axxs to drupal at borg rather than install dada on
borg.


For what it's worth, if you can understand the drupal database structure
well enough, then this dada2mir perl script might help for making a 
dada2drupal script. 
http://docs.indymedia.org/view/Devel/DadaToMir

And a rough (not just click and wait) dada2drupal script also seems
to be available:
http://lists.indymedia.org/pipermail/imc-drupal-dev/2007-May/0507-v2.html

Ah, i see you have a drupal test site and it's not quite doing what
you want:
http://lists.indymedia.org/pipermail/imc-drupal-dev/2007-February/thread.html

So i understand that you'd prefer to shift to another dada instance rather
than jumping into drupal when you're not ready.

Well, if you follow the dada security alert list, wherever that is
(and imc-security as well since at least some dada people have trouble
getting reactions from the dada mailing lists ), then i guess it probably
can't hurt. (i'm not actually on imc-security since i'm on the upstream
dev list for samizdat and any exploits would very likely go there first
rather than imc-security).


solidarity
boud


More information about the axxs-sysadmin mailing list