You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When passing both --build and --help to spin up, the application builds while also showing help output - you can see this in the details block below. One would expect the application to not build, but instead only show the help output 😅 (although admittedly this is an amusing issue to write).
$ spin up --build --help
$ spin up --build --helpspin-up Start the Spin applicationUSAGE: spin up [OPTIONS]OPTIONS: --build For local apps, specifies to perform `spin build` before running the application [env: SPIN_ALWAYS_BUILD=] --direct-mounts For local apps with directory mounts and no excluded files, mount them directly instead of using a temporary directory -e, --env <ENV> Pass an environment variable (key=value) to all components of the application -f, --from <APPLICATION> The application to run. This may be a manifest (spin.toml) file, a directory containing a spin.toml file, or a remote registry reference. If omitted, it defaults to "spin.toml" -h, --help -k, --insecure Ignore server certificate errors from a registry --temp <TMP> Temporary directory for the static assets of the componentsBuilding component hello-starling with `npm run build`
> [email protected] build
> npx webpack --mode=production && npx mkdirp target && ./tools/componentize.sh ./dist/spin.js ./target/hello-starling.wasmasset spin.js 3.53 KiB [compared for emit] (name: main)./src/index.ts 3 KiB [built] [code generated]webpack 5.90.3 compiled successfully in 628 msFinished building all Spin componentsHTTP TRIGGER OPTIONS: --allow-transient-write Set the static assets of the components in the temporary directory as writable --cache <WASMTIME_CACHE_FILE> Wasmtime cache configuration file [env: WASMTIME_CACHE_FILE=] --disable-cache Disable Wasmtime cache [env: DISABLE_WASMTIME_CACHE=] --disable-pooling Disable Wasmtime's pooling instance allocator --follow <FOLLOW_ID> Print output to stdout/stderr only for given component(s) --key-value <KEY_VALUES> Set a key/value pair (key=value) in the application's default store. Any existing value will be overwritten. Can be used multiple times -L, --log-dir <APP_LOG_DIR> Log directory for the stdout and stderr of components. Setting to the empty string disables logging to disk [env: SPIN_LOG_DIR=] --listen <ADDRESS> IP address and port to listen on [default: 127.0.0.1:3000] -q, --quiet Silence all component output to stdout/stderr --runtime-config-file <RUNTIME_CONFIG_FILE> Configuration file for config providers and wasmtime config [env: RUNTIME_CONFIG_FILE=] --sqlite <SQLITE_STATEMENTS> Run a SQLite statement such as a migration against the default database. To run from a file, prefix the filename with @ e.g. spin up --sqlite @migration.sql --state-dir <STATE_DIR> Set the application state directory path. This is used in the default locations for logs, key value stores, etc. For local apps, this defaults to `.spin/` relative to the `spin.toml` file. For remote apps, this has no default (unset). Passing an empty value forces the value to be unset. --tls-cert <TLS_CERT> The path to the certificate to use for https, if this is not set, normal http will be used. The cert should be in PEM format [env: SPIN_TLS_CERT=] --tls-key <TLS_KEY> The path to the certificate key to use for https, if this is not set, normal http will be used. The key should be in PKCS#8 format [env: SPIN_TLS_KEY=]
The text was updated successfully, but these errors were encountered:
When passing both
--build
and--help
to spin up, the application builds while also showing help output - you can see this in the details block below. One would expect the application to not build, but instead only show the help output 😅 (although admittedly this is an amusing issue to write).$ spin up --build --help
The text was updated successfully, but these errors were encountered: