There is a Bibledit version for Windows, for the Mac, for Android, for iOS, and for Linux. These are all client editions of Bibledit.
There is also a server edition of Bibledit. That is 'Bibledit Cloud'. It runs on the web. Bibledit Cloud has more capabilities than the standard Bibledit editions.
The standard Bibledit editions connect to an instance of Bibledit Cloud for collaboration, keeping the devices in sync, and for backup.
All Bibledit editions, including Bibledit Cloud, enable Bible translation. With a fast internet connection, it is usually easiest to translate straight in Bibledit Cloud through the web browser. When the internet connection is slow, or when it is off at times, it is recommended to translate through one of the standard Bibledit versions. The changes made in this way can be synchronized with Bibledit Cloud through Send/receive.
A certain release of Bibledit can upgrade the most recent previous release, but not older releases. A new release can be installed over the previous release. There should be no loss of information. Create a backup of the Bibledit folder before upgrading, just to be sure. Upgrading from Bibledit-Web to Bibledit Cloud works differently.
The various Bibledit client editions store the data offline. You can translate the Bible on a client. The user needs to regularly synchronize the data on the client with the data on Bibledit Cloud. A Client is useful when the Internet connection to Bibledit Cloud is not fast or not stable.
In the Bibledit client, connect to Bibledit Cloud once, and provide your username and password as you normally log in on Bibledit Cloud. Also provide the port number. Then synchronize the data. The first time the client will download all Bible data and Notes from Bibledit Cloud and store it offline. That may take a while. After that, synchronizing will send and receive the changes only.
The client mode is useful in a situation where the Internet connection is not optimal. All data is stored locally on your computing device. During translation, the Internet connection is not used. It is used during synchronization.
Bibledit Cloud works with email. After completing the installation of Bibledit, sending and receiving emails does not yet work. This needs to be set up. Setting up the email means to pick an email address and setting details for the mail servers in Bibledit. This can be done from within the web application.
There are two ways to have multiple translation teams on one server.
The Bibledit source code is kept in a git repository. Experienced software developers will be able to create all Bibledit editions from the source code.
To run Bibledit Cloud, a Linux VPS (virtual private server) is needed. Good providers are:
You may also run your Bibledit Cloud instance from bibledit.org. Use the contact form to explain why you need a Bibledit Cloud instance.
It is possible to enable an external OpenLDAP server for user authentication. The following file in the Bibledit installation provides all information needed: config/config.txt.
It is possible to secure traffic between a user's browser and Bibledit Cloud, and between Bibledit clients and Bibledit Cloud. The following file in the Bibledit installation provides all information needed: config/config.txt.
For better security, access Bibledit Cloud through a Tor browser.