Skip to Content
Project KeysPiping to Projects

What Is Piping?

Piping connects a workspace to directories on your filesystem. When you run lol run from a mapped directory, localWiki knows which workspace’s keys to inject as environment variables.

Setting Up a Directory Mapping

Directory mappings are configured at the workspace level (not per-project).

  1. Open Project Keys in the desktop app.
  2. Scroll down to the Project directories section.
  3. Type a directory path or click Browse to select a folder.
  4. Click Map.

localWiki writes the mapping to your workspace metadata. No files are added to your project directory.

You can map multiple directories to the same workspace. This is useful for monorepos where several services share the same secrets.

Using a Mapped Directory

Once mapped, navigate to your project directory and run any command through lol run:

$ cd ~/code/my-api $ lol run -- npm run dev

localWiki resolves the current directory to the mapped workspace, loads the keys for the selected environment, and injects them as environment variables into the child process.

Override the environment on the fly with the --env flag:

$ lol run --env staging -- npm run test:e2e

You can also override the directory or workspace explicitly:

$ lol run --dir /path/to/project -- npm start $ lol run --workspace my-team -- cargo run

Removing a Mapping

In the Project directories section, click the trash icon next to any mapped directory to remove it.

Viewing Active Mappings

Run lol status to see the current directory mapping and which workspace it resolves to:

$ lol status

Or use lol doctor for a full diagnostic that includes whether the current directory is mapped:

$ lol doctor
Last updated on