pijul nest
guest › [sign in] [explore]
{/} code [~] changes [>] discussions [*] jobs

Fork channel

Create a new channel as a copy of main.

Rename channel

Rename main to:

Delete channel

Delete main? This cannot be undone.

mode name
drwxr-xr-x scripts/
-rw-r--r-- LICENSE
-rw-r--r-- README.md
-rw-r--r-- elpegrpc.proto
-rw-r--r-- pijul.toml
README

elpe-proto

The wire contract between the Elpe frontend (the elpe CLI / OCaml recipe library) and the backend engine (elped, the Rust daemon). It is deliberately its own repository so the protocol evolves slowly and independently of either side, and so both the AGPL backend and the Apache-2.0 frontend can consume it without a license mismatch.

  • elpegrpc.proto — the gRPC service + messages.

Licensed under Apache-2.0 (see LICENSE).

How consumers find it

Both build systems resolve the proto directory the same way:

  1. ELPE_PROTO_DIR — if set, points at the directory holding elpegrpc.proto. This is the steady-state path: Elpe resolves elpe-proto like any other dependency (import → compile → run) and exports its store path here.
  2. Sibling checkout — otherwise, a checkout of this repo next to elpe-rs and elpe (i.e. ../elpe-proto). This is the bootstrap path, used before a working Elpe exists to resolve dependencies itself.

analysis_v2.proto is not here — it is a vendored, trimmed third-party Bazel aquery proto and stays with the frontend.