TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/WyattBrashear/507ex-utils2/llms.txt
Use this file to discover all available pages before exploring further.
start_server command launches a Flask web server that acts as a CAR (Central Application Repository) host for .507ex files. Once running, other machines can upload executables to it with fzx2 upload and download and run them with fzx2 exec <url>. The server stores uploaded files in a storage/ directory in the current working directory and generates a secret code for each upload that must be presented at download time.
Usage
The CLI requires a
path argument for all modes, but start_server does not use it. Pass any value (e.g., .) as a placeholder — it is ignored.How it works
Create the storage directory
If a
storage/ directory does not already exist in the current working directory, it is created. All uploaded .507ex files are stored here.Server endpoints
POST /push
Accepts a.507ex file upload and stores it in storage/. Returns a JSON response with a download URL and a randomly generated secret code.
Form fields:
| Field | Type | Description |
|---|---|---|
file | file | The .507ex file to store. |
file_id | string | The exec_id UUID read from the file’s metadata header by fzx2 upload. |
POST /pull/<file_id>
Serves the stored.507ex file for the given file_id. Requires the secret code that was issued at upload time.
Form fields:
| Field | Type | Description |
|---|---|---|
secret_code | string | The SHA-256 hash of the secret code printed by fzx2 upload. |
HTTP 401 if the secret code does not match.
Example workflow
Storage layout
After one or more uploads, the working directory looks like:.507ex file is paired with a .json file containing the SHA-256 hash of its secret code.