Differences between revisions 27 and 28
Revision 27 as of 2016-09-23 09:05:49
Size: 4608
Editor: KaiJaeger
Comment:
Revision 28 as of 2018-03-03 12:08:57
Size: 310
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
|| /!\ At present an Acre Server requires the client to use Dyalog 15.0.<<BR>>In the long run we intend to support the same versions Dyalog does support. || With version 4 acre became independent from FlipDB. It can now be used with any Source Code Management.
Line 7: Line 7:
== 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 [[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) ==
 
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.

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 ==

Link to the [[acre/ProjectPage | acre project page ]]

-- KaiJaeger <<DateTime(2014-06-05T20:48:23Z)>>

----
CategoryAcre
In fact acre itself is now developed under Git and thas therefore been relocated to [[https://github.com/the-carlisle-group/Acre-Desktop]].

The code management system acre

With version 4 acre became independent from FlipDB. It can now be used with any Source Code Management.

In fact acre itself is now developed under Git and thas therefore been relocated to https://github.com/the-carlisle-group/Acre-Desktop.

acre (last edited 2018-03-18 19:03:45 by KaiJaeger)