Public Voice Network
- ATTN: Greedy Republicans 99
- 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
- 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, 3 months ago | Thread started: Feb 18, 10, 2:29 a.m.
Out of context: Response #13 [Feb 18, 10, 2:29 a.m.]
- 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.


- View thread



