Add rokojori-auth lookup-email endpoint
Project members are currently stored by email (Option B interim). To migrate to
user-ID-based membership the two services need a server-to-server lookup call.
In rokojori-auth:
— Add POST /api/auth/lookup-email route
— Body: { email: string }
— Auth: Authorization: Bearer <SERVICE_SECRET> header (shared env var, not a user JWT)
— Returns { id, email } on success, 404 if no account exists for that email
— Add SERVICE_SECRET to rokojori-auth .env and its deployment config
In Roject:
— Add ROJECT_SERVICE_SECRET to .env (must match rokojori-auth)
— In POST /api/projects/:id/members: call account.rokojori.com/api/auth/lookup-email,
receive the user ID, store member_id as the user ID instead of the email
— In source/server/projectAccess.ts change the one line in memberMatchesUser()
from member.member_id === user.email
to member.member_id === user.userId
— Write a one-off migration script to rewrite existing project_members records:
for each member row, call lookup-email with the stored email, replace member_id
with the returned user ID
Local Git Repository Integration
Git integration inside the editor: file status indicators in the tree, staging,
commit, push, pull, diffs, and history. Depends on local filesystem access.
Once Roject can open an arbitrary local directory, the git repo is already there.
Implementation via simple-git (thin Node.js wrapper around the git CLI).
Internet Tunnel / Port Relay
Allow local devices — a Stable Diffusion instance, a local LLM, a GDScript language
server — to be accessible to authorised Roject users over the internet, routed through
the Roject server via a persistent WebSocket. Primary use case: phone as a thin client
while the main machine handles all heavy processing.
Real-Time Multi-User Collaboration
Multiple users editing the same file simultaneously with presence indicators
and conflict resolution. Likely via operational transforms or CRDTs.
Significant architecture work; not planned for the near term.
Mobile App (PWA first, native shell later)
Make Roject usable on a phone or tablet. Quickest path: PWA with a manifest
and service worker — works in Safari and Chrome on Android and iOS without an
app store. If native capabilities are later needed, Capacitor can wrap the same
web app. A React Native or Flutter rewrite is not planned.
The realistic mobile workflow is browsing files, reading output, and light edits
rather than heavy coding.