[Purebiblesearch-release] Pure Bible Search Website...

[Pure B. S. R. N. L. <pur...@li...>]

King James Pure Bible Search Users,

Last Thursday, July 16th, the SourceForge servers experienced a major
server malfunction and data storage failure, causing a massive
disruption to all projects hosted by them, including the King James Pure
Bible Search software.  I didn't become fully aware of the extent of the
outage until Sunday evening, when I realized that the King James Pure
Bible Search website was down, as the KJPBS landing page was hosted on a
SourceForge server.

Even though their techs have been working 24/7 since the failure to
restore things, large portions of the SourceForge resources are still
down, including the project website hosting and even more critically,
the project source code.  In fact, the mailing lists just came back
online today, prior to which I wasn't able to even contact any KJPBS
users to inform you about the website status.

Sunday evening, after discovering the outage, I setup a mirror for the
KJPBS website on my Amazon Web Services account, so the KJPBS website is
back online, and fully functional. However, if you tried accessing it
this past weekend or the latter half of last week and were unable to do
so, this is why.  Please try again, as things should be working now, and
please let me know if you encounter any issues.

Of the KJPBS source code, fortunately I have been keeping several
synchronized mirrors on other servers, however, there are still a
half-dozen to a dozen unaccounted for code check-ins that I'm eagerly
waiting on from their backup restoration process, which still has an ETA
of "TBD" on their status page, as the Subversion repositories (as KJPBS
is currently using) is behind the Git and Mercurial repositories in
terms of restoration priority.

This means that work on KJPBS in limbo until that gets restored.  But,
once it does get restored and I can reconcile the outstanding code
pieces, I will be looking at converting the KJPBS repository to Git,
which is a Distributed Version Control System, as opposed to the
Centralized Repository structure of Subversion.  This will make it
easier to maintain and keep live repositories running simultaneously on
multiple servers around the world, helping to eliminate development
downtime.

If any of you list subscribers are using the KJPBS source code, you will
want to keep your eyes open in the coming days to see how the KJPBS
repository will transition.  And in the meantime, get up-to-speed on Git
if you aren't already, as that will definitely be the new version
control system KJPBS will be using.

And again, sorry about the KJPBS website disruption, and any
inconveniences it caused you.
God Bless,
Donna

(You are receiving this email because you are subscribed to the
SourceForge purebiblesearch-release mailing list)