Public Voice Network
- Letterpress process video 22
- New York 44
- Pic of the Day 6329963299
- Show your latest Pics 32943294
- XBMC 33
- what happened? 2222
- F1 2012 1919
- Vid of the Day 1203312033
- the gif animation thread 1282812828
- paper trail 88
- ATTN: Greedy Republicans 88
- Facebook IPO 156156
- Diablo III 8383
- Coda 2 3434
- Chick of the Day 1537615376
- Euro Crisis 66
- In Dallas for a month 1212
- shopped? 66
- Oh Amazon. 22
- blog 5626456264
- pdf portfolio 99
- I can see it in the pixel… 1919
- TransFatty @Brooklyn Bowl 1717
- wot dis font? 11
VPS Hosting 1515 Responses
Last post: 2 years ago | Thread started: Feb 17, 10, 12:35 p.m.
- ETM
I hate to say, but Media Temple has a nice DV setup. Much, much more stable that their shared crap. Lots of nice pre-installed apps and lots of control with a user friendly interface.
I have 17 sites running on their entry level one and I rarely ever max out any resources.

- Dog-earFeb 17, 10, 1:22 p.m. – Permalink
- lukus_W
I'd be running sites built using Drupal - so I'd mainly need a LAMP stack, but I'd also initially use it as a dev sandbox to try out other packages.
I'm eventually going to start offering hosting for a small group of clients and would hope that the VPS could provide a decent way of allowing for this.
I've found webfaction are great for flexibility, and the service they offer is very good. Unfortunately I've found my account occasionally suffers from 'bad neighbour' syndrome. The solution has been to set up my own PHP stack, which goes some way to solving the problem - but I wouldn't feel happy reselling hosting from one shared hosting account.


- Dog-earFeb 17, 10, 1:57 p.m. – Permalink
- jpea
I've used slicehost for a bit, and I still use Linode for my backup nameserver, but I've moved my main things from slicehost to wiredtree.com about a year ago and haven't looked back. their datacenter is in chicago so it's a close hop to my connection and their service is stellar. I think they're a bit cheaper than slicehost and linode too...


- Dog-earFeb 17, 10, 4:01 p.m. – Permalink
- vaxorcist
Do you want to do a lot yourself? Do you want to be in charge of backups and system updates and patches? Or do you want somebody else to do that, beware of course the time involved and what happens if you mess up...
I like to roll my own dev server, but have somebody else babysit a live deployment....
so far, it looks like:
linode, slicehost = mostly roll your own
MT DV, wiredtree and others = let others manage it...

- Dog-earFeb 17, 10, 5:44 p.m. – Permalink
- ukit
Linode and Slicehost are pretty similar in that they just give you server access and you'll need to log in via command line and configure the rest.
Take a look at this page and if it doesn't scare you then you should be good to go:
http://library.linode.com/web-se…
I've actually run sites on both, but running a feature by feature comparison of the two, Linode wins out in that it gives you more RAM and bandwidth for cheaper. There is also some talk by people who have run tests that Linode's performance is better (faster) than Slicehost, although it would probably be a somewhat marginal difference. Slicehost has the advantage of offering automated backups of your site for an additional fee, which Linode does not.


- Dog-earFeb 17, 10, 8:08 p.m. – Permalink
- lukus_W
Hey again, thanks for this information - it's really helpful.
I like the idea of a managed server, but while I'm still small, I think adding extra chains in the link might actually be asking for trouble. At least if I'm looking after the server, I only have myself to blame if things go wrong.
In terms of backups and updates. I'm actually okay to do this myself I think - as long as I have access to something like aptitude (apt-get) or something similar.. I'm not sure I'd have time to regularly patch and recompile software by hand.
So, I'm thinking about Linode. I read one difference between Linode and Slicehost is that Slicehost only makes use of a 64bit kernel, which means that memory is consumed at a much higher rate. Being able to use a 32bit kernel has an advantage when dealing with lower amounts of ram - so I think I've made my choice.
Backup is now my main concern. I'm thinking Amazon S3 could be a good, cheap, solution, and I could also maintain a local rync-ed copy if I was feeling super-paranoid. I suppose the main issue is how to restore efficiently in the event of a catastrophe.


- Dog-earFeb 18, 10, 2:29 a.m. – Permalink


