Local

​

Installation

​

Usage

from mirage import RAMVFS, MountMode, Workspace
from mirage.runtime.python import LocalRuntime

ws = Workspace(
    {"/data": RAMVFS()},
    mode=MountMode.EXEC,
    runtimes=[LocalRuntime(captures=["python3", "@external"])],
)
await ws.shell("python3 -c 'print(1 + 1)'; echo hi | cksum")

import { LocalRuntime, MountMode, RAMVFS, Workspace } from '@struktoai/mirage-node'

const ws = new Workspace(
  { '/data': new RAMVFS() },
  { mode: MountMode.EXEC, runtimes: [new LocalRuntime({ captures: ['python3', '@external'] })] },
)
await ws.shell("python3 -c 'print(1 + 1)'; echo hi | cksum")

mode: exec
runtimes:
  - name: local
    captures: ["python3", "@external"]
    config:
      home: /path/to/venv/bin/python
mounts:
  /data:
    vfs: ram

​

Connecting the workspace

mounts:
  /data:
    vfs: s3
    config:
      bucket: my-bucket
    backend: fuse
    mountpoint: /data
runtimes:
  - name: local
    captures: ["python3", "@external"]

• Put the folder at the mount’s own path when you can, so a path typed in the shell names the same file in the program.
• Calls into the folder follow mount modes and policies. A folder added in code with a session, add_fuse_mount(prefix, mountpoint, session_id) or addFuseMount(prefix, mountpoint, sessionId), also follows that session’s permissions.

​

What is wired

​

Notes

• For python3, __file__ and tracebacks name the script’s workspace path, but sys.path[0] stays the host’s working directory.
• A timeout kills the subprocess.