Skip to content

About

Rewind helps close-knit groups capture everyday moments and rediscover them together through shared capsules that open at the right time.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

881 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Rewind

Rewind is a local-first SWE5006 prototype for collecting short shared moments through a group cycle, then experiencing them together after a delayed reveal.

The hosted app supports real-account sign-in and is available at:

https://d2m6kz76y4kuvm.cloudfront.net

Use that HTTPS address for the hosted app; the local URLs below are only for development.

Start the app

Use the Node.js 22 version in .nvmrc (22.23.3), npm 10 or newer, an available ffmpeg executable, and a current Chromium-based browser. With nvm, run nvm use before npm ci; the CI workflow reads the same version file.

npm ci
npm run check
make run-real

make run-real starts the local server with SQLite in .local-data/real and the Expo web app behind one same-origin proxy. Open http://localhost:8090, create an account, and sign in. New local groups use 10-minute cycles so reveal and Archive can be tested. Real sign-in normally requires HTTPS; the local exception covers plain HTTP on localhost only, so use a browser on the same machine. Press Ctrl-C to stop everything.

Optional local runtime

The companion Node service adds local SQLite persistence, media processing, and the full capsule flow. It is intended for a trusted development machine or LAN only; it is not a hosted service. Use non-sensitive test clips only.

make run is an alias for make run-real. Real sign-in needs HTTPS or localhost, so a phone on the LAN cannot sign in to this local backend; use the hosted dev URL for iPhone checks. npm run dev:lan still starts the runtime and Expo in LAN mode (REWIND_LAN_IP overrides the chosen interface) for bundling checks that do not need an account.

npm run server:preflight  # validate SQLite, LAN binding, and FFmpeg
npm run server:start      # build and run the local service

Point an iOS simulator at localhost, or a physical device at your trusted LAN address, before starting Expo:

EXPO_PUBLIC_LOCAL_BASE_URL=http://127.0.0.1:8787 npm start -- --ios --lan --clear

If the runtime is unavailable, the app keeps an explicit retryable state rather than claiming the service is connected.

Native real-account invite links require EXPO_PUBLIC_INVITE_WEB_ORIGIN to be set at app-build time to the public HTTPS origin that serves the /invite route. This is the link destination, separate from EXPO_PUBLIC_LOCAL_BASE_URL, which points to the API. Web builds use their current HTTPS origin automatically; a native build without the public origin will explain that invite links are unavailable instead of sharing an API URL.

The HTTP boundary has bounded defaults in both local CLI and Compose runtime modes: 30 seconds of request-body idle time, 120 seconds per media upload, two concurrent media intakes, and one concurrent media processor. Override them with REWIND_HTTP_IDLE_TIMEOUT_MS, REWIND_HTTP_UPLOAD_TIMEOUT_MS, REWIND_HTTP_MAX_CONCURRENT_INTAKES, and REWIND_HTTP_MAX_CONCURRENT_PROCESSING when a trusted runtime needs different bounds. JSON bodies remain capped at 64 KiB and staged media at 50 MiB. Slow or aborted bodies use a deterministic 408 response when the connection is still writable, oversized bodies use 413, and capacity rejections use 429; there is no distributed rate limiter.

Media defaults to REWIND_MEDIA_BACKEND=disk, preserving the staged intake and filesystem rollback. local enables immutable private object references under the data directory; it requires REWIND_MEDIA_ENVIRONMENT (for example, test). The same configured store is used by HTTP retrieval, clip workers and the cycle scheduler. Local stores retain the authenticated staged-upload path.

The opt-in s3 backend additionally requires REWIND_MEDIA_S3_BUCKET, REWIND_MEDIA_S3_OWNER (12-digit expected owner) and REWIND_MEDIA_S3_REGION. Optional REWIND_MEDIA_S3_KMS_KEY_ARN must be a canonical key ARN. The SDK uses its standard credential provider chain; credentials are not application settings. Construction sends no cloud requests. Signed PUT intents bind incoming bytes, checksum and version; retrieval stays behind the application's authorization boundary. A provider environment still needs separately verified private bucket versioning, encryption, lifecycle and browser CORS before this mode is usable. Local tests do not establish those provider guarantees.

Weekly reminders are opt-in and have no automatic service or timer. Configure REWIND_REMINDER_EXPO_ENABLED=true (optionally REWIND_REMINDER_EXPO_ACCESS_TOKEN) and/or the complete REWIND_REMINDER_VAPID_SUBJECT, REWIND_REMINDER_VAPID_PUBLIC_KEY, and REWIND_REMINDER_VAPID_PRIVATE_KEY set. Provider construction sends no requests; an explicit bounded pass runs with:

npm run server:build
node server/dist/cli.js reminders --once --json

An unconfigured pass is a no-op. The API registers a device destination against its authenticated real-account session; it never returns the destination or provider credentials in status responses. Only enabled, unsnoozed members with an active registration session are eligible at Sunday 19:00 in the group's timezone, with a 24-hour catch-up limit. Logout, session expiry, membership changes, and destination rotation fence queued work. Registrations therefore require a current session and must be renewed after session expiry.

One outbox job is created per group/member/local Sunday. Sends retry at most three times; Expo tickets are polled separately without resending accepted tickets. A crash after provider acceptance can still cause a retry, so provider sends are at-least-once. Provider acceptance does not establish phone delivery. Web Push currently accepts Apple, Mozilla, and Google push endpoints. Client permission/registration, actual provider delivery, and hosted acceptance remain separate prerequisites; this command does not provision or schedule a worker.

Current scope and limits

  • Real capture requires a camera; iPhone camera capture needs the hosted HTTPS app.
  • Locally, group media stays on the local runtime. Do not use real or sensitive media.
  • Hosted persistence and recovery are separate from this local quick start; follow the guarded deployment guide before operating the hosted host.

Checks

npm run check             # format, lint, architecture, types, and tests
npm run test:responsive   # web layout checks at supported viewports
npm run server:preflight  # local runtime, SQLite, LAN, and FFmpeg readiness

Further reading

About

Rewind helps close-knit groups capture everyday moments and rediscover them together through shared capsules that open at the right time.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages