Alright, separating out by functionality is just fine. But you all act as if a VPS is a single point of failure. This isn't completely true. In a sense, if the host machine fails your instance is down until it is migrated. The last time this happened my site was down for 5 minutes and they called me to let me know what was happening before I knew about it. The RAID is not local to the box, it is network based. <br>
<br>As for showing work, while I feel I have shown what I can do, this is obviously not quite enough yet. <br><br>So I am not discounting any ideas here, I just want everyone to be on the same page on redundancy for a VPS provider (a good one, not the $5 FSCK VPS services out there).<br>
<br>I will be working on the Drupal site because everyone wants results, including me. Work has been done to get things setup, so the first step is complete. I have verbal promises that I will get the Drupal 7 work sent to me and that will help accelerate this. I invite anyone who would like to also contribute to let me know so I can setup an account and I won't be blocking your ability to work. <br>
<br>Dan Kulinski <br><br><div class="gmail_quote">On Wed, Feb 15, 2012 at 9:00 AM, David L. Willson <span dir="ltr"><<a href="mailto:DLWillson@thegeek.nu">DLWillson@thegeek.nu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
...<br>
<div class="im">> > wait, they didn't support email (and I, for one, didn't want to<br>
> > lose the mailing list). So people<br>
> > expected to build a Drupal site that would replace the current one,<br>
> > and save us money on hosting<br>
> > too. But the email obstacle was a bridge too far. And it wasn't<br>
> > bypassed, overcome, or let be--the<br>
> > project died.<br>
><br>
> Then I would say the "drupal folks" need to work on resolving that<br>
> issue as part of the drupal solution.<br>
</div>...<br>
<br>
I think I disagree. I think web folks don't need to worry about email. If I haven't said so out loud already, I think separating email server from web server is a good idea, or at worst, a neutral idea.<br>
<br>
It seems to me that it could go something like this: a motivated web-dude puts up a new web-site, on a web-server with sufficient resources for his platform of choice. We love it. We re-point the A records and call it good. The MX record remains un-changed until someone changes it. Or have I misunderstood something this basic all these years?<br>
<br>
Then, someone raises the point that the web-site is on a single-spindle POS in someone's basement, and do we really want to do it that way, at which point, we copy the thing to RDR's mega-box, add another A record and call it better. The MX record continues to trundle along happily. Yes? No?<br>
<br>
Advantage of the -admin list: Being able to be blunt, or RDR-blunt, which is a whole different kind of blunt. :-)<br>
Disadvantage of the -admin list: Lurk-listen-and-learn much less likely here.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
clue-admin mailing list<br>
<a href="mailto:clue-admin@cluedenver.org">clue-admin@cluedenver.org</a><br>
<a href="http://cluedenver.org/mailman/listinfo/clue-admin" target="_blank">http://cluedenver.org/mailman/listinfo/clue-admin</a><br>
</div></div></blockquote></div><br>