Working alongside Agrafe

Eqlat reads deployments from Agrafe; Agrafe stays the place where projects are written and deployed.

Deployments and tokens

Everything Eqlat queries is a deployment. In Agrafe:

• Deploy creates a new deployment, with a new id and new tokens. It shows up in Your Deployments, under its project.
• Update recompiles a deployment from the current files. The id, the tokens and the data are kept, so Eqlat keeps working with the token you already gave it.
• Tokens lists a deployment’s tokens; + Token issues a new one, Revoke disables one. A revoked token is refused the next time Eqlat checks it, and the token form comes back.

The query builder’s choices follow the deployed schema: after an Update, reload the query page to see new concepts and properties.

Public projects

A project switched to Public in Agrafe is listed on Eqlat’s Public Projects page, and its deployments can be queried without a token. See Public projects.

Prefixes

The short names in the results use the namespaces of the deployed project, as Agrafe compiled it. After changing them in Agrafe, Update the deployment.

Other apps

The Apps menu in the top bar switches to the other Dolfin apps, including Owlograf, which draws a project as a graph, and Pangloss, which shows it as a glossary.

Feedback and updates

The Feedback tab on the left edge sends a message to the Dolfin team with a screenshot you can crop. When Eqlat is updated while you have it open, a banner offers Reload.