Create a New Project Key
Open your workspace in the localWiki desktop app and navigate to Project Keys in the sidebar. Click Add key to open the creation form.
Fields
- Name — the environment variable name. Use uppercase with underscores by convention (e.g.
API_BASE_URL). - Value — the secret or configuration value. This field is masked by default.
- Environment — select a single target environment:
development,staging, orproduction. Each key belongs to exactly one environment. To use the same variable name across environments, create a separate key for each. - Description — optional free-text field. Use this to explain what the key does, where to get a new value, or link to relevant docs.
- Visibility — controls whether the value can be revealed in the UI. Keys marked
revealableshow an eye icon in the list.
Example
To add a database connection string for development:
| Field | Value |
|---|---|
| Name | DATABASE_URL |
| Value | postgresql://dev:pass@localhost:5432/myapp |
| Environment | development |
| Description | Local Postgres instance. Run docker compose up db first. |
Avoid storing large blobs (certificates, private key files) as project keys. Use the Secrets Vault for those — it handles binary data and has its own encryption layer.
Editing and Deleting
Click the edit icon on any key in the list to open the edit form. When editing, the environment and name fields are fixed — you can update the value, description, and visibility. Changes are saved immediately and synced to workspace peers.
To delete a key, click the trash icon on the key row and confirm.
Environment Filtering
The key list shows an environment badge next to each key (D for development, S for staging, P for production). Use the filter dropdown to show only keys for specific environments.
Conflict and Staleness Indicators
Keys that have diverged across devices show a conflict badge. Keys not updated for more than 7 days show a stale warning. Both are visible directly in the key list.