Repository navigation
release: demoflow 0.7.1 - #391
Open
AndreyBegma wants to merge 116 commits into
Open
AndreyBegma wants to merge 116 commits into
AndreyBegma wants to merge 116 commits into
Conversation
docs: Phase 8 — share links, website editor, scheduled checks
The runtime stage copied .next/standalone and .next/static but not public/, which the standalone output leaves out, so /demo/landing.mp4 and its poster answered 404 on staging and production. status.sh now also requests /demo/landing-poster.png and exits non-zero unless every public path answers 200, and refresh.sh waits for the web container to serve the poster before it records the deploy. Closes #370
…mage-does-not-serve C-193: fix(web): the Docker image does not serve apps/web/public — landing video 404
…meline The project config gains render.endHoldMs (0-10000, default 2500): how long a successful video keeps the result on screen after the last step. Every step accepts hold (100-10000 ms), refused on an off-camera step, and a timeline event records the hold it kept as holdMs. Schemas regenerated (spec 365).
… the relay The Share model and its migration hold one shared render per run and format. The runner protocol gains share.prepare, share.prepared and share.error, the poster asset on video.open and the features list on launches.sync. VideoRelay can now pull a whole file into disk through the same streams, credit and timeouts that playback uses.
A step with hold keeps the page on camera that long after its action, stamps holdMs on its event and keeps endMs at the action's end. After the last step of a run that passed, RunOptions.endHoldMs (default 0) is slept before the recording closes; demoflow run passes render.endHoldMs. A failed step holds nothing, and a page that leaves during a hold fails the step it held (spec 365).
…in-defaults-to-stagi C-192: fix(cli): demoflow login defaults to staging instead of production
docs: Glass UI redesign and adding a project from the website
A share is created with POST /shares (or POST /runner/shares from the machine that reported the run), checked against the file limit and the account quota, and answered 202 while the API pulls the poster and the render through the runner socket into SHARE_DIR. The share turns ready when both files are on disk, or failed with a short code; a failed or lost share of the same render is replaced by the next POST. The owner lists, reads, extends (30 days at a time, at most 90 ahead) and revokes shares. Deleting a run, a project or the account removes the share directories after the rows. A sweeper deletes expired shares, fails stuck uploads and orphan directories, and marks a ready share whose file is missing as lost at boot. The run page reports the features the machine announced, so the web can offer sharing only when the daemon supports it.
…ction The API image creates /data/shares owned by node so a new named volume starts writable. Both stacks mount the shares volume there, set SHARE_DIR, and document the file limit and the quota in their env examples. deploy/README.md explains the volume, the limits, the sweeper and that shared videos are not backed up.
…r rendering A check runs one scenario, or with no scenario every scenario of the project against one start of the app, with record: false and no render. It prints a line per scenario and the totals (or one JSON object with --json), exits 0 when every run passed and 1 otherwise, and reports each run with kind: 'check'. --format, --headed, --run-id in a pass and --exclude beside a scenario are refused before anything runs (spec 360).
launches.sync now carries checks: true when the daemon handles launches. A check.start is checked like a run.start: exactly requestId, rootPath and exclude, a registered root, and at most LIST_MAX_SCENARIOS valid scenario ids. A refusal answers check.error and spawns nothing; a valid request spawns run --check --json --progress --project <root> with one --exclude per id, answers check.started, then check.finished with the pass's counts. The 15-minute launch cap restarts with each scenario, and the whole pass is capped at two hours (spec 360, Decision 6).
…zoomed assertion The plan ends at the last event plus its hold and render.endHoldMs (0 after a failure), clamped to the source, replacing the fixed 1 s tail. Hold windows count as active so the idle trim never cuts them, and an assertion with zoom keeps the camera and an outline on its element through its hold.
Why hold and not wait: the idle trim shortens a wait on a still page, never a hold.
CLI test projects set endHoldMs to 0 to keep runs short; one test checks the default reaches the plan.
Bumps @andrewbehma/glass-ui to 0.37.0 for use-breakpoint (spec #373, Decision 7) and adds the pure modules the shell is built on, each with a node:test suite.
The test asserted that stderr never matches /report|500|runner\/runs/i, but stderr carries 'Running <scenario> (<run id>)' and the run id holds the UTC time as HHmmss. Any run started at hh:50:0x or 15:00:xx printed '500' and failed the test on any OS; the Windows failure in #387 started at 12:50:08. The test now pins that run id, so the case is exercised on every run, and matches 500 only as a number of its own, plus the server URL itself. Refs #387
chore(cli): bump demoflow to 0.7.1
Every /app page now renders inside one shell: a glass sidebar with the brand, the nav and the machine status, a top bar with the breadcrumb and the account menu, the verify-email banner and one content column. Narrow screens open the same navigation in a bottom sheet. The theme is System, Dark or Light from the account menu. An inline script sets it before first paint and follows the OS while on System. The Overview gets stat tiles for projects, runs and failing projects. Pages drop their own back links and outer columns, and project and run pages name their breadcrumb segments instead of showing ids.
…-glass-ui-app-shell-glass-sideba
…un-s-video-share-model C-190: feat(api): share a run's video — Share model, disk storage, upload through the runner socket, limits
planChapters takes the plan's scene cards at their output start, after the idle map and every earlier card, so a chapter lands where the card is drawn. The FFmpeg renderer records them on every format it writes (spec 349, Decision 1).
…-add-project-dialog-machine-path
…-share-dialog-on-the-run-page-an
Signs in off camera, opens the Add project dialog from the Projects page and closes it with Escape. It touches only what renders on an empty account. Refs #379.
The daemon announces features: ['share'] and answers share.prepare with the scenario's description, the render's chapters and the size of a poster it makes with FFmpeg (one JPEG frame, at most 1280 px wide, reused while newer than the render). The relay serves that poster for video.open with asset: 'poster'; an unknown asset is not-found. scenarioDescription moves to scenario-file.ts so the daemon reads descriptions the way demoflow render does.
…ule rules The client gains the schedule, health and stale routes of spec #362, the run kind and the project stale count. lib/schedule.ts maps the form to the PUT body, validates the time, words the next check and orders the health list, covered by schedule.test.mjs. The copy for the whole of spec #363 lands in en.ts.
…ject page The Scheduled checks card sits under the project header: set, edit and remove the website schedule, show a config schedule read-only with a link to the docs, and warn when a schedule is paused. Below it the health list shows each scenario as stale or passing, stale rows first, with a link to the last run.
… on /app The project list shows "N stale" next to a project with broken scenarios. A check run carries a Check label in the run library, and its run page says it records no video instead of showing the player, the format switch or the download. /app lists up to ten stale scenarios, says "All passing" when a user with a schedule has none, and hides the block for a user without one.
…dule-in-demoflow-confi C-184: feat(core,cli): schedule in demoflow.config.json — the runner daemon runs checks on a schedule
The scenario signs in off camera, creates a project and opens it to show the Scheduled checks card in its unbound state, which renders for any account.
The command resolves the run like demoflow render, finds its server id in the reported-runs index, posts /runner/shares with the device token and polls the share every second for up to ten minutes. Server refusals become exit-2 CommandErrors with their codes; an existing share is kept and printed; a failed upload exits 1. --password is asked for without echo on a terminal, else read from DEMOFLOW_SHARE_PASSWORD, and never taken as a flag value.
share_demo creates a share link for a reported run without a password, only when the run's project sets share.allowMcp: true. It waits up to 50 s for the upload and answers uploading when the runner is still at it.
…-add-a-project-from-the-website # Conflicts: # apps/api/src/projects/projects.service.ts # apps/api/src/runner/runner-connections.service.ts # apps/api/src/runner/runner-socket.ts
…ject-from-the-website feat(api): add a project from the website — machine, local path, GitHub link
…log-on-the-run-page-an C-185: feat(web): Share dialog on the run page and the /app/shares list
…-add-project-dialog-machine-path
…edules-on-the-project C-179: feat(web): check schedules on the project page and stale badges
…-the-runner-uploads-a-render-for
…ct-dialog-machine-path C-195: feat(web): Add project dialog — machine, path, inspection result, create config, GitHub link
…project-from-the-websi C-194: docs(web): adding a project from the website and allowed roots
…r-uploads-a-render-for C-186: feat(cli): the runner uploads a render for a share; demoflow share and the MCP share_demo tool
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
demoflow logindefaults to production (fix(cli): demoflow login defaults to staging instead of production #369)apps/web/public: the landing video works (fix(web): the Docker image does not serve apps/web/public — landing video 404 #368)apps/cli0.7.0 → 0.7.1: release.yml publishes it and tags v0.7.1.