AutoCua
Automate with computer-use agent (ComputerUse / CUA) for macOS, Windows, Linux, Browser, iOS & Android. It sees the screen, clicks, types, browses and writes the code too. One agent, every computer.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證使用 Next.js、Express、Prisma 和 Socket.io 建構的多人看板。
AI 翻譯
Multi-user Kanban board built with Next.js, Express, Prisma, and Socket.io
正在載入完整 README。 以下為已儲存的摘錄。
4. Point the frontend at your local backend
frontend/src/lib/api.ts hardcodes the deployed API, so a local frontend talks to
the deployed backend rather than the one you just started. Change baseURL to
http://localhost:4000/api (or whatever PORT the backend logs) while working
locally.
Sign in. npm run db:seed creates one admin user, [email protected], with the
password set in backend/prisma/seed.js. Change it after your first sign-in —
that password is committed to this repository, and the account is the super-admin
that the admin screens exempt from every guard.檢視完整 README ↗cd backend && npm install
cd ../frontend && npm install
cd backend
npm run db:push
npm run db:generate
npm run db:seed
Terminal 1 (Backend):
cd backend && npm run dev
Terminal 2 (Frontend):
cd frontend && npm run dev
frontend/src/lib/api.ts hardcodes the deployed API, so a local frontend talks to
the deployed backend rather than the one you just started. Change baseURL to
http://localhost:4000/api (or whatever PORT the backend logs) while working
locally.
Sign in. npm run db:seed creates one admin user, [email protected], with the
password set in backend/prisma/seed.js. Change it after your first sign-in —
that password is committed to this repository, and the account is the super-admin
that the admin screens exempt from every guard.
The seed only runs against an empty database: it counts users first and skips if any exist. So it will not reset a password or recreate a user you deleted, and it is safe to leave in the backend's start command.
Every in-app notification (ticket assigned, @mention, PRD approval requested,
PRD section to complete, PRD approved, PRD changes requested) is also emailed to
the recipient through Resend. Email is best-effort: if it
fails, the error is logged and the in-app notification still goes out. The code
is in backend/src/lib/email.js.
Backend environment variables (Railway → backend service → Variables):
| Variable | Required | Notes |
|---|---|---|
RESEND_API_KEY | yes | From Resend → API keys. Without it, emails are skipped. |
EMAIL_FROM | for real use | e.g. FluxusTeam <[email protected]>. Must be on a domain verified in Resend. The default [email protected] only delivers to the Resend account owner's own inbox. |
FRONTEND_URL | no | Base for links in emails. Defaults to https://fluxusteamkanban.vercel.app. |
EMAIL_NOTIFICATIONS | no | Set to off to pause emails without removing the key. |
The sending domain does not have to be the app's domain: the app can stay on
vercel.app while mail is sent from a domain you own (e.g. fluxx.ng), once
that domain's DNS records from Resend → Domains are added at its registrar.