[Imc-drupal-dev] Drupal IMC Hosting Followup

[mark burdett]

Hi, i just found out that the ISP for one of my personal servers wants 
me to commit to a higher bandwidth usage level.. which is encouraging me 
to find more sites to put on it.  But, I would not actually recommend it 
to any IMCs since it's just my box, so you're relying on me not to drop 
off the face of the earth, and i might/would get grumpy since i actually 
have to pay for the bandwidth.

Probably the best thing for me to do would be to offer a varnish proxy 
for sites that could use it, that way no one is really counting on me 
for everything.  I just added it to 
http://docs.indymedia.org/view/Devel/IMCServerOffers

--mark

On Thu, 20 Nov 2008 14:17:54 +0100, ekes wrote:
> 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
> 



> _______________________________________________
> Imc-drupal-dev mailing list
> Info: https://docs.indymedia.org/view/Devel/ImcDrupalDev
> Imc-drupal-dev at lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-drupal-dev