railgrid sandbox
Drive a development-mode instance: sync, exec, logs, restart, status
Synopsis
Drive a development-mode infrastructure Instance (for an App Studio project, <project>-dev) through the hub data plane, as you.
Component paths are relative to the component’s workspacePath: for the application template, sync api/ to component “api” and web/ to “web”. Production instances answer 409.
railgrid sandbox sync shop-dev api ./api
railgrid sandbox exec shop-dev api -- node -e 'console.log(1)'
railgrid sandbox logs shop-dev api -f
railgrid sandbox restart shop-dev api
railgrid sandbox env shop-dev api PULSE_URL=https://… --restart
railgrid sandbox status shop-dev [api]railgrid sandbox [flags]Options
-h, --help help for sandbox
--org string Organization display name or UUID (default: the org that owns the kubeconfig's workspace)
--workspace string Workspace display name or UUID (default: the workspace the kubeconfig points at)Inherited options
--insecure-skip-tls-verify Skip TLS certificate verification when talking to the hub
--kubeconfig string Path to the kubeconfig file (default: $KUBECONFIG, then ~/.kube/config)See also
- railgrid — railgrid: an open-source control plane for platform teams
- railgrid sandbox env — Set environment variables on the component’s running dev process
- railgrid sandbox exec — Run a command in the component and exit with its exit code
- railgrid sandbox logs — Print the dev process log
- railgrid sandbox restart — Restart the component’s dev process
- railgrid sandbox status — Show the instance status, or a component’s process state
- railgrid sandbox sync — Push a directory into the component workspace (authoritative)