Skip to content

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

IdentityContext

Hosted CLI sign-in for WikiContext, NotifyContext, TaskContext, DealContext and VaultContext at https://id.pocketcontext.com. IdentityContext uses PocketContext and its default users collection. Read docs/protocol.md for the protocol and deployment contract.

Develop and validate

Install with uv pip install -e . or build with uv build. The client command is identitycontext login --email you@pocketcontext.com; whoami and logout take that same explicit email. The reusable library powers the supported application clients.

Build the server commit in POCKETCONTEXT_VERSION using its documented Go/CGO commands. Run from this application directory with isolated storage:

/path/to/pocketcontext serve --dir /private/path/pb_data --http 127.0.0.1:8097
python3 -m unittest discover -s tests -v
python3 tests/integration.py --binary /path/to/pocketcontext
python3 tests/oauth_integration.py --binary /path/to/pocketcontext

Tests use synthetic accounts, temporary databases, a local Google provider fixture and a mocked external signing boundary. They never call live Google or OCI signing. Production OAuth and HSM verification are separate deployment gates.

Default-users authentication hooks were adapted from RaiseContext; the hosted identity protocol and client are independent. The browser vendors PocketBase SDK 0.28.1 under its MIT license in pb_public/POCKETBASE-LICENSE.md.

Full release validation additionally runs:

npm ci
npx playwright install chromium
python3 tests/browser.py --binary /path/to/pocketcontext
python3 tests/launcher.py
uv build
docker build -t identitycontext:ci .
python3 docker/smoke.py config --image identitycontext:ci
python3 docker/smoke.py smoke --image identitycontext:ci
python3 docker/smoke.py restore --image identitycontext:ci

The signing unit tests require cryptography; no OCI credentials are used. Browser tests use Playwright and a local synthetic provider, never live Google. See deployment and recovery before provisioning or releasing. The new app's source is public; deployment configuration and all credentials stay in the private scaffold. Shared CLI sessions contain sensitive tokens and never belong in Git, logs, telemetry or support messages.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages