AutoCua
macOS·Windows·Linux·브라우저·iOS·Android용 컴퓨터 사용 에이전트(CUA)로 자동화
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기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.