mounts:runtimes:?The engines a line can run on. Both python engines are registered — monty and pyodide — and this entry says which one python and python3 bind to; quickjs takes node and js. All are sandboxed, so their file I/O only reaches the mounts above. The builtin command engine is always present, so it is not listed. - { name:, captures: [python, python3] } - { name: quickjs, captures: [node, js] } # Route to e2b sandbox if python script has NumPy, see route.py - name: e2b?Runs python that needs more than a browser has. Connect a store and a key, then put the script and its data where both sides can reach them:$ cp /repo/stats.py /repo/prices.csv /redis/$ python3 /redis/stats.py captures: [python, python3] config: { apiKey: } route_policy: ?A different door: asked once per line, before anything runs, and answering who runs it rather than whether it may. A runtime name places the line, a deny refuses it. It outranks the runtimes above and yields to a runtime named on the call. clis: simple: script: ?The program, run on the engine named beside it.runtime: quickjs profiles: admin: commands:allow: [,,,,,,,,,,,,,, ] policy:?A program the gate runs before every command this profile runs. It sees the command's context and reads the filesystem, and answers allow, ask or deny. script: ?The program, run on the engine named beside it.runtime: monty user: commands:allow: [,,,,,,,,,, ] policy:?A program the gate runs before every command this profile runs. It sees the command's context and reads the filesystem, and answers allow, ask or deny. script: ?The program, run on the engine named beside it.runtime: monty mounts: /tmp: mode: read paths:hide: [, ]?Built on the real @struktoai/mirage-browser. Every command runs Mirage in your browser.
A real Virtual Terminal, running in browser?Built on the real @struktoai/mirage-browser. Every command runs Mirage in your browser.