# Build File uploads You were asked to build the spec `vex/file-uploads`, version 0.1.2, from Spekkr. Uploads that go straight from the browser to your storage, with size and type checks, private downloads and nothing left orphaned. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/vex/file-uploads/start.md`, before you go on. Published by vex, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `file-uploads`, inside the project you are working in. ```sh mkdir -p file-uploads && curl -fsSL https://spekkr.com/vex/file-uploads/bundle.tar.gz | tar -xz -C file-uploads ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/vex/file-uploads/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `vex/file-uploads` and the person's choices. ## 2. Record the person's choices Write `file-uploads/spekkr.inputs.json`. With every default it is: ```json { "spec": "vex/file-uploads", "version": "0.1.2", "inputs": { "allowed_types": "image/png,image/jpeg,application/pdf", "database": "postgres", "image_previews": false, "max_file_mb": "25", "scan_hook": false, "storage": "s3_compatible" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `max_file_mb`, Largest file, in megabytes: any text. - `allowed_types`, File types allowed: any text. - `image_previews`, Small previews of images: `on` or `off`, written `true` or `false`. - `scan_hook`, Hold files until they are scanned: `on` or `off`, written `true` or `false`. - `database`, Database: one of `postgres`, `sqlite`. - `storage`, Where files are kept: one of `s3_compatible`, `local_disk`. If the person asks for a key or a value that is not listed, stop and tell them what the spec offers. ## 3. Build The files named below are the ones now in `file-uploads`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `spec.md`: Requirements and acceptance criteria. - `design.md`: Data model, rules and flows. - `tasks.md`: Build tasks in order, each with a check.