The code management system acre

$/!\$ At present an Acre Server requires the client to use Dyalog 14.1.
In the long run we intend to support the same versions Dyalog does support.

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?
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?
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?
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?
to upload your changes automatically into the main repository and get support (comparison tools etc.) when there is a conflict?
to restore effortless any old version from the main repository?
to go back to any older version since you’ve checked out your copy?
an insurance against aplcores, “Dyalog has stopped working” and disappearing Dyalog sessions?
to abandon the need of saving (possibly corrupted) workspaces?

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.

Watch acre in action

PhilLast and KaiJaeger have given a presentation on acre at the Dyalog conference 2014 in Eastbourne / South England.

How to get it (download)

Acre is a simple and small namespace that contains all the code. It was written by PhilLast on behalf of Carlisle Group in order to support the international development team of FlipDB.

Acre is free even for commercial usage, although the license under which it is provided has some limitations. See AcreLicense for details.

To take full advantage of its power you also need an AcreServer running somewhere, typically in the cloud. Acre Server is owned by Carlisle Group. Luckily Carlisle have agreed to offer a free version of the Acre Server as well. It is a fully fledged relational database management system written in Dyalog that supports all the functionality required by acre. Acre Server is available for download from its home page.

Go to download page

How to start using acre

Create a folder on your machine that will function as your project library. We will assume that the name will be Foo\.
Download the file acre.zip from this page.
Move the contents of that zip file into Foo\.
- At this stage you have 4 folders and one file in your project folder Foo\:
- Acre\
- acre.ini
- Conga\
- APLTreeUtils\
- APLTreeHelp\
Fire up an instance of Dyalog 14.1 or better.
Load the workspace "Foo/acre/acre.dws".

At this stage you can start using acre. Ask for advice with

    #.acre.Help''

You can also download any member of the APLTree project with acre. The INI file contains the necessary pieces of information for this:

[Acre]
ipaddress  = acreserver.does-it.net   ⍝ was once acre.aplwiki.com
portnumber = 59753
username   = default
password   = default

For example, try this:

      #.acre.GetProject'WinFile'

Using acre with a backend repository

In order to take full advantage of acre you need to have an acre repository running somewhere. See the page AcreServer for details.

History of acre

Acre was originally developed to support the international FlipDB development team. From 2008 it was used to manage the FlipDB project.

In 2014 Carlisle Group, the owner of acre, decided to provide acre as a free tool to the APL community via the APL Wiki. In September 2014 all the APLTree projects were converted into acre projects. That has not changed the way people can download such projects from the wiki, but it has changed the way developers are expected to cooperate while working on an APLTree project.

See TheAPLTreeProjectAndAcre for details.

Project page

Link to the acre project page

-- KaiJaeger 2014-06-05 20:48:23

CategoryAcre

-  ⇤ ← Revision 2 as of 2014-06-05 20:48:23 → 
  Size: 2143
  Editor: KaiJaeger
  Comment:
+   ← Revision 26 as of 2015-12-02 11:08:55 → ⇥
  Size: 4608
  Editor: KaiJaeger
  Comment: New version: requires now 14.1
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+<<TableOfContents>>
-Line 2:
+Line 4:
+|| /!\ At present an Acre Server requires the client to use Dyalog 14.1.<<BR>>In the long run we intend to support the same versions Dyalog does support. ||
-Line 5:
+Line 9:
- * 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?
+Do you want...
-Line 7:
+Line 11:
- * 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?
+ * to store the source code and associated files of Dyalog APL projects in a database (repository) running somewhere, typically the cloud, supporting multiple developers?
-Line 9:
+Line 13:
- * 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?
+ * 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?
-Line 11:
+Line 15:
- * 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?
+ * 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?
-Line 13:
+Line 17:
- * Want to upload your changes automatically into the main repository and get support (comparison tools etc.) when there is a conflict?
+ * 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?
-Line 15:
+Line 19:
- * Want to restore effortless any old version from the main repository?
+ * to upload your changes automatically into the main repository and get support (comparison tools etc.) when there is a conflict?
-Line 17:
+Line 21:
- * Want to go back to any older version since you’ve checked out your copy?
+ * to restore effortless any old version from the main repository?
-Line 19:
+Line 23:
- * Want an insurance against aplcores, “Dyalog has stopped working” and disappearing Dyalog sessions?
+ * to go back to any older version since you’ve checked out your copy?
-Line 21:
+Line 25:
- * Don’t want to save workspaces any more?
+ * an insurance against aplcores, “Dyalog has stopped working” and disappearing Dyalog sessions?

 * to abandon the need of saving (possibly corrupted) workspaces?
-Line 25:
+Line 31:
-== How to get it ==
+== Watch acre in action ==

PhilLast and KaiJaeger have given [[https://www.youtube.com/watch?v=sGQSmHuQSb8 | a presentation]] on acre at the Dyalog conference 2014 in Eastbourne / South England.

== How to get it (download) ==
-Line 27:
+Line 37:
-acre is a simple and small namespace that contains all the code. It is free. Soon you will be able to download from here.
+Acre is a simple and small namespace that contains all the code. It was written by PhilLast on behalf of [[https://www.carlislegroup.com/ | Carlisle Group ]] in order to support the international development team of FlipDB.
-Line 29:
+Line 39:
-To take full advantage of its power you also need a [[FlipDB]] database server running somewhere. FlipDB is the flagship of [[https://www.carlislegroup.com/ | 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.
+Acre is free even for commercial usage, although the license under which it is provided has some limitations. See AcreLicense for details.

To take full advantage of its power you also need an AcreServer running somewhere, typically in the cloud. Acre Server  is owned by Carlisle Group. Luckily Carlisle have agreed to offer a free version of the Acre Server as well. It is a fully fledged relational database management system written in Dyalog that supports all the functionality required by acre. Acre Server is available for download from its home page.

|| [[attachment:acre.zip | Go to download page ]] ||

== How to start using acre ==

 1. Create a folder on your machine that will function as your project library. We will assume that the name will be Foo\.
 1. Download the file acre.zip from this page.
 1. Move the contents of that zip file into Foo\.<<BR>><<BR>>
    At this stage you have 4 folders and one file in your project folder Foo\:
    * Acre\
    * acre.ini
    * Conga\
    * APLTreeUtils\
    * APLTreeHelp\
 1. Fire up an instance of Dyalog 14.1 or better.
 1. Load the workspace "Foo/acre/acre.dws".

At this stage you can start using acre. Ask for advice with 

{{{
    #.acre.Help''
}}}

You can also download any member of the [[CategoryAplTree | APLTree]] project with acre. The INI file contains the necessary pieces of information for this:

{{{
[Acre]
ipaddress  = acreserver.does-it.net   ⍝ was once acre.aplwiki.com
portnumber = 59753
username   = default
password   = default
}}}

For example, try this:

{{{
      #.acre.GetProject'WinFile'

}}}


== Using acre with a backend repository ==
In order to take full advantage of acre you need to have an acre repository running somewhere. See the page AcreServer for details.

== History of acre ==
Acre was originally developed to support the international FlipDB development team. From 2008 it was used to manage the FlipDB project.

In 2014 Carlisle Group, the owner of acre, decided to provide acre as a free tool to the APL community via the APL Wiki. In September 2014 all the [[CategoryAplTree | APLTree]] projects were converted into acre projects. That has not changed the way people can download such projects from the wiki, but it has changed the way developers are expected to cooperate while working on an APLTree project.

See [[TheAPLTreeProjectAndAcre]] for details.

== Project page ==
-Line 33:
+Line 97:
-Link to the [[FlipDB/ProjectPage | FlipDB project page ]]
-Line 35:
+Line 98:
+----
CategoryAcre