This also highlights the problem with the autochecker for updates. We should
simply just not do it.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Chris Meller
Sent: 27. oktober 2008 23:10
To: Habari - Dev; [email protected]
Subject: [habari-dev] Re: Habari Server Move

 

Just as an update, someone has already reported on IRC that Habari 0.5.x has
a problem related to fetching updates when you visit the dashboard and your
server has not yet noticed the change. This will prevent your dashboard from
loading, but the navigation menu and the rest of the admin should function
normally. Visitors to your blog should not be affected. This issue has been
corrected in the latest trunk development code for quite some time now, but
has not been rolled into a final release yet.

For those geekier types, the new IP is 208.78.101.56, if that helps you.

On Mon, Oct 27, 2008 at 5:30 PM, Chris Meller <[EMAIL PROTECTED]>
wrote:

I just wanted to let everyone know that earlier today we made a server
switch. Due to some DNS limitations we weren't able to make it as quick and
painless as we'd hoped, so all the Habari sites (habariproject.org, trac,
svn, wiki, etc.) may be unavailable to you for several more hours.

If your DNS hasn't updated you'll simply get a page telling you to check
back later, so if you still see the site you were expecting you're good to
go. Please don't hesitate to let us know if you run into any kind of problem
- nothing like this is ever foolproof.

A special thanks to Matthias Bauer (moeffju) for providing us with hosting
up to this point. We will always appreciate his help getting us on our feet
as we moved off Google Code and will likely continue to abuse his generosity
in the future. :)

Thanks!

Chris Meller





--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/habari-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to