The code management system acre

Overview

Do you want to store the source code and associated files of Dyalog APL projects in a database (repository) running somewhere, typically the cloud, supporting multiple developers?
Want to store private copies of such a project independently from the main branch in the same repository as an insurance against, say, the loss of your laptop?
Want to save all versions of APL objects and files of a project locally until it’s time either to back them up into your private part of the repository or merge them into the main branch?
Want to have reports about what you've changed, what was backed up, what’s causing a conflict, who has changed what and when in the main branch, which of your changes, if any, will cause a conflict on upload?
Want to upload your changes automatically into the main repository and get support (comparison tools etc.) when there is a conflict?
Want to restore effortless any old version from the main repository?
Want to go back to any older version since you’ve checked out your copy?
Want an insurance against aplcores, “Dyalog has stopped working” and disappearing Dyalog sessions?
Don’t want to save workspaces any more?

If so then acre is for you. But be warned: once you’ve started working with it you won’t want to go back. Ever.

How to get it

acre is a simple and small namespace that contains all the code. It is free. Soon you will be able to download from here.

To take full advantage of its power you also need a FlipDB database server running somewhere. FlipDB is the flagship of Carlisle Group. Luckily they have agreed to offer a free version of FlipDB as well. This will be a stripped down version of FlipDB but it is still a fully fledged relational database system written in Dyalog. FlipDB will soon be available for download from here as well.

Link to the acre project page

Link to the FlipDB project page -- KaiJaeger 2014-06-05 20:48:23