reelmimic
좋아하는 영상을 보여주면 같은 스타일의 새 영상을 AI 팀이 함께 기획·제작·검토해 줍니다
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기A personal library for manga, books, and CDs. Browse visual shelves, find missing volumes, and revisit the memories behind every haul.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Your collection, and the stories behind it.
Atelier Strawby is a personal library for manga, light novels, books, and CDs. Its collection view, Strawby Stacks, brings your shelves together with cover art, edition details, acquisition dates, and the memories attached to each physical copy.
Visit Strawby Stacks · User guide · Local setup & deployment
The shared shelf is read-only, and notes stay private unless you choose to share them. Collection management lives at /edit, protected by owner-only Cloudflare Access. Write APIs, imports, and backups also verify the owner’s identity. Access configuration.
| Layer | Technology |
|---|---|
| Application | Astro 5, React 19, TypeScript |
| Styling | Tailwind CSS 4 and custom CSS |
| Hosting | Cloudflare Pages |
| Data | Cloudflare D1 with Drizzle ORM |
| Artwork | Private Cloudflare R2 storage, served through the app |
| Owner sign-in | Cloudflare Access |
| Verification | Node test runner, Playwright, axe |
Optional metadata comes from MangaDex, Google Books, Open Library, MusicBrainz, and Cover Art Archive, with a labeled digital iTunes fallback. Suggestions are reviewed before saving; manual entry remains available when a provider is unavailable.
Use Node.js 22.18+ and npm. From a fresh checkout:
git clone https://github.com/jhsu22/atelier-strawby.git
cd atelier-strawby
npm ci
cp .dev.vars.example .dev.vars
npm run db:migrate:local
npm run seed:local
npm run dev
Open http://127.0.0.1:4321. The example environment enables editing only on localhost. Preserve an existing .dev.vars and .wrangler directory when returning to an established checkout.
The included CSV seeds 177 manga copies across 38 series. Repeating the same import preserves owner edits and does not add duplicate copies.
Local development uses emulated D1 and R2. Local state and the hosted collection are independent. An optional Google Books key belongs in .dev.vars; see the Google Books setup guide.
npm run validate # Lint, type checks, unit/integration tests, schema, build
npm run test:d1 # Tests against the local Cloudflare runtime
npm run test:e2e # Desktop/mobile browser and accessibility checks
npm run release:verify runs the complete release checks, including migration verification. Browser tests create disposable seeded D1/R2 state. They use system Chromium when available; otherwise install it with npx playwright install chromium. Use STRAWBY_TEST_PORT=4337 if the development server already occupies port 4321.
For anonymous shelf and access-denial checks:
STRAWBY_TEST_READ_ONLY=true STRAWBY_TEST_PORT=4337 npx playwright test public-access.spec.ts
The app runs on Cloudflare Pages with separate production and preview D1 databases and private R2 buckets. The checked-in wrangler.toml points to this installation; configure your own bindings, canonical origins, owner identity, and Access policy before deploying a fork. Keep credentials in Cloudflare secrets or ignored local environment files.
Follow the deployment guide for provisioning, migrations, publishing, backups, and rollback, and the public viewing and owner editing guide for the /edit Access policy. JSON backups contain artwork references; R2 image bytes need a separate backup.
| Guide | What you’ll find |
|---|---|
| User guide | Browsing, editing, imports, and backups |
| Deployment | Local setup and Cloudflare operations |
| Public access | Shared shelves and owner-only management |
| Released volumes | Edition matching, missing volumes, and catalog limits |
| Barcode scanning | Scanning manga ISBNs, matching, measured accuracy, and the recognition roadmap |
| Architecture | Application structure and service boundaries |
| Data model | Catalog entries, editions, and owned copies |
| Directory structure | Where code, tests, and assets live |
| Testing | Verification procedures and recorded results |
| Security review | Recorded findings and operational considerations |
Stage reports in docs/ preserve development history and the verification results recorded at each stage.