Dokkit Claim a name soon

DokkitLibraries

Libraries

Eleven languages, one file each, and the same calls in all of them: start, beat, job, capture, and a way into the language's own logging where it has one.

The same calls, eleven times

Install, start, beat, job, capture and logging, written the way each language writes them. Pick a tab.

clients/ · 11 libraries

Add yours

None of them is on a package registry yet. Each one installs from a clone of the repository, the way its own README says.

What they all do

  • With no address or key, every call does nothing. Each one reads DOKKIT_URL and DOKKIT_KEY.
  • None of them raises an error into your app. If the server cannot be reached, the app carries on.
  • An error report carries the error's type and stack, never its message.
  • A version sends one deploy line, and the server records a deploy only when the version changes.
  • A line over 64 KB is cut, and its message ends in [cut].

A machine with the dokkit program on it can report a job with dokkit run instead, which also keeps the last lines of its output.

Next:

Let an agent wire it inOne prompt adds the library and proves it Install the serverSo the calls have somewhere to go Back to the startWhat Dokkit is, and the working sample