[Purebiblesearch-release] Pure Bible Search Source Repository...
GUI Application to Search and Count the Pure King James Bible
Brought to you by:
dewhisna
|
From: Pure B. S. R. N. L. <pur...@li...> - 2015-08-03 01:19:55
|
King James Pure Bible Search Users, This email is targeted to those using the King James Pure Bible Search source code for their own development purposes: As you'll recall from my previous email to this list, the SourceForge servers suffered a major storage system malfunction on Thursday, July 16th. It seems they have successfully gotten things recovered and restored, at least in all areas that affect King James Pure Bible Search. However, this outage has prompted me to implement the source code repository restructuring I have been contemplating for some time now. While I had synchronized backups of the previous repository, there was no automated system to keep them up to date. As such, I nearly lost the details of seven code commits and would have if SourceForge hadn't been able to restore from their backups. Thankfully, those have been recovered. The previous KJPBS code repository was using Subversion for source control management. The biggest problem or shortcoming with Subversion is that it's a centralized repository, meaning only one server can be the "keeper of the data" and if that server or the link to that server is down, then no work can be committed on the project until it's restored. Until July 16th, the central Subversion repository for KJPBS was SourceForge. Being unable to work on KJPBS code during this outage prompted me to finally rebuild the code repository to use Git source control management. Git is a distributed repository system where every checkout of the code is a complete and self-contained repository clone, allowing work to continue even when all internet traffic is down. And multiple hosting servers can be setup to mirror the data and automatically synchronize with one another -- meaning multiple definitive sources instead of one. Or as Pastor Mike would put it: "two or more witnesses". I will continue to host KJPBS on SourceForge, but as a Git repository instead of Subversion. And I have established an account on GitHub and set it up as a second Git repository for KJPBS. The old Subversion repository (named "code") on SourceForge is still currently there, but is set as read-only and serving only as a backup for the time being. If you are currently using the KJPBS source code base, you'll want to switch to the new code repository as soon as possible, as no more updates will be made to the Subversion repository going forward. And at some point, I will eventually delete the Subversion repository. To move to Git, you will need to install a Git client (see https://git-scm.com/) and clone the repository either from SourceForge or from GitHub. The following URLs are the online source browsers for the new KJPBS repositories and contain the corresponding URLs needed for cloning: SourceForge Git Repository: https://sourceforge.net/p/purebiblesearch/KingJamesPureBibleSearch/ GitHub Repository: https://github.com/dewhisna/KingJamesPureBibleSearch/ The last part of the URL is the name of the repository itself, which is "KingJamesPureBibleSearch" on both systems. SourceForge is more project based and GitHub is more user based, meaning SourceForge has it filed under the project name of "purebiblesearch" and GitHub has it under my username of "dewhisna". Either repository can be used and should contain the same data, as I plan to set things up to simultaneously push all commits and updates to both servers. For all end-users not using the KJPBS source code, this email probably means very little to you. All software downloads and online access can still be accessed via the main website page as always: http://www.PureBibleSearch.com/ God Bless, Donna (You are receiving this email because you are subscribed to the SourceForge purebiblesearch-release mailing list) |