EveryDocumentation 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.
.507ex project must contain a file named exactly runfile — no extension — in the root of the source directory. It holds a single shell command that FZX2 runs after it extracts the archive into a temporary runtime directory. Without this file, fzx2 build refuses to proceed and raises a FileNotFoundError. The command is passed directly to subprocess.run with shell=True, so the full shell feature set — pipes, redirects, environment variables, and shell builtins — is available.
Requirements
- The file must be named
runfilewith no file extension. - It must be located in the root of the source directory (the directory you pass to
fzx2 build). - It must contain a single shell command on one line.
- It is required. Building without it raises
FileNotFoundError: No Runfile Detected!
Format
The file contains one shell command. No shebang, no comments, no blank lines are needed — just the command..fzx2-runtime/<exec_id>/, where <exec_id> is the UUID stored in the 507ex-id metadata field.
Examples
Because
shell=True is set, shell pipelines, redirects (>), and environment variable expansion ($VAR) all work exactly as they would in a terminal.What happens at execution time
Extract the ZIP payload
FZX2 extracts the archive into
.fzx2-runtime/<exec_id>/. All files from your source directory — including runfile itself — are available there.Project structure example
The following project structure produces a valid.507ex file when built:
runfile containing:
fzx2 build my_project packages everything into my_project.507ex. When executed, FZX2 extracts the archive and runs python3 main.py from the runtime directory.