<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
I've only been at Slicehost for a couple months and I haven't had any
issues yet. The server uptime, billing, and support have been great.
Upgrading a slice from 512MB to 1GB worked flawlessly and relatively
quickly. Backup snapshots of the slice work like a champ. The admin
system isn't bad. It's clean and easy to use. The Ajax terminal is
slick. You can use Slicehost to manage your DNS, which I do, but it is
a little cumbersome at first. They also have a bunch of good articles
on installing various web servers and such. The Slices are 64-bit and
the server on my slice has 4 CPUs/cores of which I am guaranteed one of
them, but can use more CPU if the other slices aren't busy.<br>
<br>
In the end, I have had a really great experience so far. I pay
$87/month for a 1GB slice, backups, and a second IP address. I figure
that isn't that bad since I figure it was costing me about that much
when I was hosting stuff out of my house and had to deal with business
class internet, power consumption, and hardware failures.<br>
<br>
-Chris<br>
<br>
<br>
Eric F Crist wrote:
<blockquote
id="mid_066B6EAF-A97E-49E5-9234-D821152C4743_secure-computing_net"
cite="mid:066B6EAF-A97E-49E5-9234-D821152C4743@secure-computing.net"
type="cite">
<pre wrap="">Why Slicehost?
/me reads...
* Choice of Linux distro.
Crap.
Oh yeah, this is a Linux list.
:)
But, seriously, all seriousness aside, what were your pluses and
minuses for Slicehost?
Thanks,
Eric
On Sep 21, 2008, at 11:14 PM, Jordan Peacock wrote:
</pre>
<blockquote id="StationeryCiteGenerated_1" type="cite">
<pre wrap="">Thank you all for the feedback. I've talked to/played with a few
potentials and am going to do Slicehost for the largest site....and
the rest of them once I figure out how to neatly consolidate things.
Thanks to all, and to all a good night.
======================
Jordan Peacock
<a class="moz-txt-link-abbreviated" href="mailto:hewhocutsdown@gmail.com">hewhocutsdown@gmail.com</a>
hewhocutsdown.blogspot.com
On Sun, Sep 21, 2008 at 9:59 AM, Eric F Crist <<a class="moz-txt-link-abbreviated" href="mailto:ecrist@secure-computing.net">ecrist@secure-computing.net</a>
</pre>
<blockquote id="StationeryCiteGenerated_2" type="cite">
<pre wrap="">wrote:
Any recommendations?
It's for an existing site that exceeds the CPU/RAM usage of some
</pre>
</blockquote>
<pre wrap="">of the
</pre>
<blockquote id="StationeryCiteGenerated_3" type="cite">
<pre wrap="">lower-priced basic offerings from AN Hosting or GoDaddy (the
</pre>
</blockquote>
<pre wrap="">shared virtual
</pre>
<blockquote id="StationeryCiteGenerated_4" type="cite">
<pre wrap="">servers). Not a heavy hard drive or bandwidth site. Currently paying
$150/quarter, looking to lower that as much as possible, as this
</pre>
</blockquote>
<pre wrap="">is for a
</pre>
<blockquote id="StationeryCiteGenerated_5" type="cite">
<pre wrap="">non-profit organization that is on half of a shoe-string budget as
</pre>
</blockquote>
<pre wrap="">it is.
</pre>
<blockquote id="StationeryCiteGenerated_6" type="cite">
<pre wrap="">Does it make sense to upgrade my internet connection and host it
</pre>
</blockquote>
<pre wrap="">myself, or
</pre>
<blockquote id="StationeryCiteGenerated_7" type="cite">
<pre wrap="">go after a hosting company? Ideally I would like to administrate
</pre>
</blockquote>
<pre wrap="">the server
</pre>
<blockquote id="StationeryCiteGenerated_8" type="cite">
<pre wrap="">as well and have it run Ubuntu or Debian, but I'm not hellbent on
</pre>
</blockquote>
<pre wrap="">that.
Sorry I'm coming into this late. If you're not experiencing huge
bandwidth requirements from any of the sites you're hosting, I'd
recommend DSL and hosting things at your own home, provided you have
space. As you suggest this above, I'm guessing this isn't a problem.
For many, many, years, I've hosted my things on a server in my own
basement. I've got DSL from ipHouse (iphouse.net), and very
reliable power in my neighborhood. Comcast is even allowing
webhosting on their connections now, provided you go with the
business-level service. With that, you can get blocks of IPs, the
same as has been the case with DSL for years. Their upload speed
ranges from 1 to 2 Mbps, whereas DSL caps out at ~800Kbps. Qwest is
offering a new 20Mbps fibre option, but I'm not sure about their
terms on personal web hosting.
If that doesn't work for you, I know of at least one person who uses
Colo Pronto (<a class="moz-txt-link-abbreviated" href="http://www.colopronto.com">www.colopronto.com</a>) without too much issue. You ship
down your own 1u server, pay $25/mo and you get a 100Mb connection
to the world (shared, of course). They make their money on service,
however. Reboots, eyes and hands, etc. I'd caution you on them
only in regards to outgoing spam. UCEPROTECT has them listed at
various levels on a fairly regular basis, a few times at level 3
(the entire AS was blacklisted).
Now, when you run you servers at home, there is going to be the
occasional downtime. No, or little, battery backup; no connection
redundancy; you're out of town on vacation and cannot reboot that
firewall you *had* to reconfigure from the beach. Overall, I find
it's nice to have control of things.
---
Eric Crist
_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<a class="moz-txt-link-abbreviated" href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a>
</pre>
</blockquote>
<pre wrap=""><!---->
---
Eric Crist
_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<a class="moz-txt-link-abbreviated" href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a>
</pre>
</blockquote>
<br>
</body>
</html>