We are running on a new webserver as of this morning.  I do have to admit, I could have done a little better on communication for the outages.  I did FB and Twitter about what was going on consistently on the BT FB/Twit page - even a post in TriTalk, but that probably doesn't get 3/4 of the users.

I need to do a better job in employing the 'persistent header' for problems - even if I think it will be resolved quickly.  And I did underestimate this.  Even when we had the new server ready late yesterday afternoon, I didn't realize that we had the entire filesystem on the webserver - I assumed it was on the good, database server.  So it took many, many hours last night to copy all pictures, attachments, routes, uploads to the new server - meanwhile, the old, flaky webserver went offline twice during this.  Then once the transfer of files was done (about half a million), copying over all of the webserver files - which goes a lot quicker.

What can be done to prevent this?  There are a few different sever configurations that we can utilize...though it will mean probably getting another server to sit around, though read-to-go.  It's more money but it may be worth it.

So...I'm sorry.

Verified some bug fixes just now, hope to have them live in the next few days.  Next round of mobile updates will be on our dev server in a few days, these include some forum thread and search additions, purchasing bronze/silver memberships on mobile, viewing and importing bronze/silver training plans on mobile.