Dinoer

Guides

Install Dinoer, run it, launch a research campaign, write scenarios, set up the encrypted directory. Each guide gives commands you can type.

Two installation channels: the .deb package to use Dinoer as it is, a Git clone to modify it. Install covers both.

The lock you will meet first

Dinoer refuses to run for an agent that cannot quote the version number of its guide. Without the option, the answer is this (real output):

{"succes": false, "erreur": "guide_non_lu", "guide_version_attendue": "1.6"}

The lock relies on cooperation: it makes skipping the guide a deliberate act, and does not stop anyone set on deceiving it. Why it exists →

Credentials never pass through your shell

A scenario names the key; the value stays in the encrypted directory and is read inside the browser process:

{"type": "remplir", "selecteur": "input[name=\"password\"]",
 "valeur": "depuis_secrets", "secret_cle": "password"}

Where passwords live, and the mistake that writes them in clear →

Where to start

First time: Install, then First run, which ends with a real answer from your own machine.

A research question rather than a single page: Running a research campaign.

A task in several steps to automate: Writing a scenario.

Something that does not work: Recipes, sorted by symptom.

In detail