When working with a SADE instance users usually start manipulating the output, preparing own transformations or want to use a different configuration for the Lucene index. These changes should be tracked in a version control system like git and should be deployed to a standalone application that does not interfere with others.

That's why SADE offers a mechanism to fork any instance at any state. Developers can use this to continue development and for new users it offers a playground for testing purposes.

At the SADE Publisher within the TextGridLab enter a new project name at the input field in the first panel (1). Forking step 1

Click on "create" (2) and wait until you get redirected to your own instance.

The resulting view should present new credentials at the top. Again you have to set these credentials in the preferences in TextGridLab.

Download & Tracking changes

You can download any application by clicking on the download button at the SADE Publisher GUI. This gives you a XAR package according to the EXPath package standard (which is in fact a ZIP archive).

When any further development is planned, fork the offical SADE repo from clone the repo to your local machine and replace the files with those from the XAR archive. This is for complete upstream compatibility.

When you want to publish your fork in the SADE group (for example to make it part of the reference instance) you have to rename the repository.