Get started
how to use Tuttle?
in the pictures below the Github Logo is used but Gitlab can be used the same way
From Git to eXist-db
With ‘Git to DB’ editors will work with their own tools and push changes to Git. The data are kept in Git and are deployed to eXist-db on demand or automatically by an Git action. Data can be updated completely or incrementally just applying the changes since last update.
There is a simple dashboard to trigger the updating of data and checking the status of connected repositories.
When opening the dashboard the status of the configured repositories is requested. The colors of of the rows signal the status of the respective repository.
| color | Status |
|---|---|
| orange | new - the repository is configured but has not yet been deployed into TEI Publisher. The ‘incremental’ button is disabled as the data need to be checked out before. |
| green | up-to-date - the are no differences between data in the database and the repository. ‘Incremental’ can be used to trigger update of differences. |
| blue | behind - the data in the database are behind the status in the repository. An update is needed |
| red | error - a configuration or connection problem occured |
From application to Git
Configuration is the same as with ‘Git to DB’.
The difference is in which part of the Tuttle API is used by the consumer (the application). In this mode a application may offer a button to allow users to trigger the pushing of changes to a Git repository.