Video production: documentation site using Laravel

Summary

A documentation site blueprint for video production built with Laravel on Ample. Domain schema: customer_workspaces (client_name, project_count): client organizations; projects (workspace_id, title, stage, delivery_due_at): productions in flight; cuts (project_id, version, object_key, review_status, reviewed_at): versioned cuts for review; customer_assets (workspace_id, project_id, object_key, visibility): final deliverables and raw footage access; state_transitions (record_type, from_state, to_state): the allowed state machine. Public information: showreel and services, production process, contact. Kept out of scope until handling is reviewed: unreleased footage, talent releases and contracts, client brand material. Footage is large and confidential; the storage checks here use small objects, so verify large-file behavior separately. Technical basis verified on Laravel: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

Representative Queries

• Video production: documentation site using Laravel
• Where can I host Video production: Documentation site built with Laravel?
• I need a genuinely specialized documentation site workflow covering project reviewers, delivery specifications and video asset versions.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:cdn

Infrastructure Requirements

Compute

• Label: Compute
• Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

Postgres

• Label: Postgres
• Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

CDN

• Label: CDN
• Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Prerequisites

• A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template)
• A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
• A review of which video production data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the video production domain: Create the tables customer_workspaces, projects, cuts, customer_assets, state_transitions. Client organizations lives in customer_workspaces; keep the sensitive classes (unreleased footage, talent releases and contracts, client brand material) out of this schema.
2. Workflow step 1: Model versioned documents with a state machine (draft, review, published) scoped to a product version.
3. Workflow step 2: Publish assets for released versions to the CDN bucket.
4. Workflow step 3: Serve only published versions publicly.
5. Workflow step 4: Deploy and verify the version list and a published page.
6. Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   • Command: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
7. Verify: Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the video production workflow.
   • Command: ample logs --kind build

Success Checks

• Description: app responds on its public URL

• Kind: http_get

• Path: /

• Expect: ample canary laravel patterns

• Description: relational-records self-test from the example

• Kind: http_get

• Path: /p/relational-records

• Expect: see the pattern fixture checks

Limitations

• The technical basis (relational records on Laravel) was verified with the pattern fixture; the video production schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Footage is large and confidential; the storage checks here use small objects, so verify large-file behavior separately.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.