upgrade to 3.0
This commit is contained in:
20
content/blog/2013-04-24-dear-hosting-provider.md
Normal file
20
content/blog/2013-04-24-dear-hosting-provider.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: 'Dear Hosting Provider'
|
||||
date: '2013-04-24T14:44:48-04:00'
|
||||
permalink: /dear-hosting-provider/
|
||||
tags:
|
||||
- grousing
|
||||
- networks
|
||||
---
|
||||
|
||||
Weirdly, when our team <del datetime="2013-04-24T20:38:16+00:00">said “let’s upgrade our server”</del> got a message saying “we’re going to upgrade your server,” we didn’t expect you to redirect our DNS entry to a machine so new that it has no files on it. Not just no files, but no configuration whatsoever. And no users, so no way to, I don’t know, *configure* the machine such that one can put *files* on it.
|
||||
|
||||
I know. Silly us.
|
||||
|
||||
No worries, though. It’s not like we were running a large-scale scholarly community that depends on the goodwill of its volunteer participants, whose goodwill varies directly with the perceived stability of the platform.
|
||||
|
||||
Thanks, however, for giving the team a bit of clarity on the whole “hey, do we want to stay with this hosting provider or look for another one that might be better suited to our needs” business!
|
||||
|
||||
Love,
|
||||
@kfitz
|
||||
|
||||
Reference in New Issue
Block a user