.env with loopback UI/API origins, a disposable PostgreSQL database and a unique POSTED_SECRET. Run the API, UI and worker in separate terminals:
Integration services
The test suite creates a separate random PostgreSQL schema per test file and removes that schema afterwards. Its default development database ispostgres://posted:posted-local-verification@127.0.0.1:55490/posted. Override DATABASE_URL for your disposable local database.
The S3 integration tests create and remove a random bucket in a local RustFS instance. Their fixed credentials are disposable test credentials, not production secrets. Run the fixture services:
pnpm verify. POSTED_TEST_STORAGE_ENDPOINT may override the storage endpoint, but tests refuse non-loopback storage. RustFS fixture configuration follows its official Docker guide.
Browser preview fixtures
Use a disposable loopback installation with the API and UI origins set tohttp://localhost:4341 and http://localhost:4342. After configuring .env and starting the integration services, prepare private preview storage and sample data:
posted-preview bucket, local CORS and a sample image in artifacts/posted-preview.png. Configure the preview’s S3 variables to use that bucket and the disposable storage credentials above. The account helper rejects production and non-loopback installations. It creates a verified preview administrator, fake provider connections and display-only API-key/MCP records whose hashes cannot authenticate requests. Sign in with local@avgeek.ltd and test123. The short password is assigned only by this guarded local fixture; normal setup and password-change validation still apply.
Start pnpm dev:preview and pnpm dev:web for browser review. Add connection uses the production UI and copy. Continue opens a local provider authorization page; Authorize and Cancel return through the production callback, including actor-bound expiring state, one-use authorization codes, verifier checks and connection persistence/reconnection. Only the external provider transport is simulated. The preview API enables all four providers and creates disposable accounts without external sign-in or publishing access. It keeps normal session, administrator and origin checks, rejects production, non-loopback origins and any workspace other than Posted Preview, and does not run an email or delivery worker. Production and ordinary pnpm dev still require configured provider OAuth credentials. Preview provider credentials are deliberately unusable; do not run pnpm dev:worker against this database. Worker/container verification uses a separate empty database.
What the tests prove
- First-administrator setup requires the installation secret and does not send verification email.
- Roles govern scheduling, uploads and account management.
- Concurrent requests produce one group and one delivery per selected account; content mismatches conflict. Partial success preserves successful provider results without republishing either account.
- Scheduled edits use version guards and independently replayable request keys.
- Competing workers cannot share a claim. Expired preparation can recover; uncertain publishing never blindly requeues.
- Provider contract tests use strict request stubs, with no fallback to real provider networking.
- The official MCP SDK exercises consent, PKCE, user-selected scopes, request keys and role-change revocation through Posted’s HTTP handlers.
- Real S3 operations cover private access, signed uploads, immutable originals, verified bytes and bounded reads.
- Sharp tests cover all four providers’ output formats, byte limits, dimensions, orientation and metadata removal.
Video media
Install FFmpeg and ffprobe on the development host (brew install ffmpeg on macOS). The worker image supplies FFmpeg from Alpine. The existing worker prepares private video uploads before claiming delivery jobs. Give it a writable /tmp of at least 256 MiB; Compose sets this explicitly while retaining the read-only root filesystem. Upload completion returns 202 while a video is processing. Poll /api/media/{id}/status for ready metadata or a failed response. Originals remain private and immutable; the worker produces a metadata-stripped H.264/AAC MP4 with inline playback support.
The browser preview processes media through the same preparation function, but continues to leave the delivery queue untouched. Do not start the real publishing worker against browser fixtures. Existing image tables and associations are renamed by migration 007 without replacing their records or stored objects. Post/draft contracts use media and mediaIds; upload routes use /api/media. MCP supports reserving/completing private uploads and checking their status and preview.
Documentation and release preparation
Edit the guide sources indocs/*.md and product configuration in docs/site.json. Run pnpm docs:build to generate Mintlify pages with the shared docs kit. pnpm docs:check checks generated consistency, schemas, links and screenshot dimensions; pnpm docs:validate runs the pinned Mintlify build and broken-link checks. Review pnpm docs:dev on desktop and mobile.
pnpm docs:preview starts an isolated fixture schema and bucket on ports 4391/4392 for documentation captures. It uses sample accounts and media, processes media only and removes its owned data when stopped. It does not reset an existing preview installation.
Run pnpm verify and pnpm verify:production before requesting release review. The production gate creates disposable containers, verifies setup, private video, scheduling, branded account email and database/media restoration, then removes its containers and private files. Native AMD64 and ARM64 CI are required before publication. The release workflow validates the exact source commit, scans images, checks anonymous GHCR access and writes an immutable three-image manifest. See the repository’s release sign-off report for the current candidate status.