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.
upload command reads the unique exec_id from a .507ex file’s metadata header, prompts you for a CAR server address, and POSTs the file to the server’s /push endpoint. The server responds with a download URL and a secret code. You share the URL and code with anyone who needs to run the executable — they pass both to fzx2 exec.
Usage
Path to a local
.507ex file built with fzx2 build. The file must exist and contain a valid 507ex-id metadata field.How it works
Validate the file path
fzx2 checks that the file exists. If it does not, the command exits immediately with File not found!.Read the exec_id from the metadata header
The file is scanned line by line until a line beginning with
507ex-id| is found. The UUID following the pipe character is used as the file_id sent to the server.Prompt for the server address
http://192.168.1.50:5000.POST to /push
The
.507ex file is sent as a multipart upload to <server>/push with the file_id field included in the form data.Example terminal session
Server response format
The/push endpoint must return a JSON object with at least the following fields:
Sharing the result
Once the upload completes, share the URL and secret code with the recipient. They run:Errors
| Message | Cause |
|---|---|
File not found! | The specified .507ex path does not exist. |
The secret code is generated by the CAR server at upload time. Keep it confidential — anyone with both the URL and the secret code can download and execute the file.