[linksunten-technik] Sweet land of liberty

[Bartolomeo]

Moin,

also...

FTP (File Transfer Protocol) over SSH (Secure Shell): Eine sehr sichere 
Methode, mit der wir Dateien auf den Server hochladen können
* http://de.wikipedia.org/wiki/File_Transfer_Protocol
* http://de.wikipedia.org/wiki/SSH

MySQL (My Structured Query Language): Ein relationales Datenbanksystem, das 
wir für Drupal 6 brauchen
* http://de.wikipedia.org/wiki/MySQL

DNS (Domain Name Service): Das ist ein Dienst, der URLS in IP-Adressen auflöst 
(z.B.: tachanka.org -> 216.254.116.241)
* http://de.wikipedia.org/wiki/Domain_Name_System

> und von wem kams jetz? den united kollektives?

Von ekes von IMC York.

> wie sieht das mit traffic und sowas aus? 

Keine Ahnung, schauen wir mal. Das ist ja sowieso erstmal nur ne Lösung für 
den Produktionsserver, also dem Server, der die HTML-Seiten erstellt. Vor dem 
NATO-Gipfel brauchen wir unbedingt eine dezentrale Mirror-Struktur, wie z.B. 
hier beschrieben:
* http://docs.indymedia.org/view/Sysadmin/DrupalForAMajorConvergence

> und wo steht der server dann nochmal?

In New York, siehe auch:

----------  Weitergeleitete Nachricht  ----------

Betreff: Re: [Imc-drupal-dev] Drupal IMC Hosting Followup
Datum: 20.11.2008, 14:17:54 Uhr
Von: ekes <ekes at aktivix.org>
An: imc-drupal-dev at lists.indymedia.org

robbt at azone.org wrote:
> I'll see if anyone has server space to host
> a lot of new IMCs with Drupal, 

The only host I know of so far is meuse.tachanka.org it's a (US based)
vserver on https://aerosan.tachanka.org/wiki/PublicServices so we aren't
talking a lot or big here. I could also do non-EU ones on
http://forest.aktivix.org/ which is a dedicated (old) box in a UK colo,
but has a whole sack full of other drawbacks...

> otherwise this should be our first priority,
> finding a server to set-up new IMC sites.

It would be nice. Admin'ing such a thing is a bit of a sucky job though
- I already think the two servers above are more than I can handle
personally.

I think the only way of doing it is maintaining a version of core that
can be upgraded by the admins, but you still need to give freedom to
people to install modules... this really puts you in a security
blackhole as most site admins don't upgrade properly. I guess setting up
some server separation maybe php-cgi etc. is the only way :-(

> So the next step beyond the hosting would be actual development.
> I suggest we utilize Drupal 6.0. I would be happy to use this as a
> motivating factor behind my own redesign/upgrade of our IMC site to Drupal
> 6.0 and set-up something. We just need to develop the
> documentation/architecture etc and then code it into a install profile and
> set it up for people. 

We've discussed install profiles before. The problem is that just the
workflow for posting/reporting/promoting/hiding/...
articles/newswire/features/... is so different between sites - some
people can do it with workflow, some people use the hidden module, some
people use the scotland module etc.

It really makes little sense to create a one-size-fits-all install
profile - it will remove the one thing that's good about Drupal the
flexibility and ease of setting up to ones needs.

What would be way more useful is a set of how-tos for different tasks:
setting up publishing workflow; setting up video; setting up images;
setting up spam filtering; securing the site etc.

Cheers,

ekes

-------------------------------------------------

> Ich würde noch die Frage anschließen, wieviel das jetzt kostet?

Erstmal nix. :-)

Ciao, Bart
-- 
http://keys.indymedia.org/cgi-bin/lookup?op=get&search=0237D46E
eMail: bartolomeo at indymedia.org + Jabber: bartolomeo at jabber.org