@tildacloud/cli
v0.61.0
Published
A new CLI generated with oclif
Readme
@tildacloud/cli
A new CLI generated with oclif
Usage
$ npm install -g @tildacloud/cli
$ tilda COMMAND
running command...
$ tilda (--version)
@tildacloud/cli/0.61.0 darwin-arm64 node-v22.21.1
$ tilda --help [COMMAND]
USAGE
$ tilda COMMAND
...Commands
tilda build qwiktilda deploytilda deployment-key createtilda help [COMMAND]tilda logintilda logouttilda pluginstilda plugins add PLUGINtilda plugins:inspect PLUGIN...tilda plugins install PLUGINtilda plugins link PATHtilda plugins remove [PLUGIN]tilda plugins resettilda plugins uninstall [PLUGIN]tilda plugins unlink [PLUGIN]tilda plugins update
tilda build qwik
Build a Qwik application for deployment to Tilda
USAGE
$ tilda build qwik --apiOrigin <value> --projectDir <value> [--json] [--inlineIdentityJson <value>]
[--authToken <value>]
FLAGS
--apiOrigin=<value> (required) [default: https://tilda.net, env: TILDA_CLI_API_ORIGIN] API origin
--authToken=<value> [env: TILDA_CLI_AUTH_TOKEN] Private key config. Must be of type { privateKey: string,
keyId: number } encoded in base64
--inlineIdentityJson=<value> [env: TILDA_CLI_INLINE_IDENTITY_JSON] Private key config. Must be of type { privateKey:
string, keyId: number }
--projectDir=<value> (required) [default: .] Path to the Qwik project directory
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Build a Qwik application for deployment to TildaSee code: src/commands/build/qwik/index.ts
tilda deploy
Build the application
USAGE
$ tilda deploy --apiOrigin <value> --projectDir <value> --project <value> --site <value> --runtime
nodejs22.x|nodejs24.x [--json] [--inlineIdentityJson <value>] [--authToken <value>]
FLAGS
--apiOrigin=<value> (required) [default: https://tilda.net, env: TILDA_CLI_API_ORIGIN] API origin
--authToken=<value> [env: TILDA_CLI_AUTH_TOKEN] Private key config. Must be of type { privateKey: string,
keyId: number } encoded in base64
--inlineIdentityJson=<value> [env: TILDA_CLI_INLINE_IDENTITY_JSON] Private key config. Must be of type { privateKey:
string, keyId: number }
--project=<value> (required) Project slug
--projectDir=<value> (required) [default: .] Relative path to project directory
--runtime=<option> (required) [default: nodejs22.x] Runtime
<options: nodejs22.x|nodejs24.x>
--site=<value> (required) Site slug
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Build the applicationSee code: src/commands/deploy/index.ts
tilda deployment-key create
Create a deployment key
USAGE
$ tilda deployment-key create --apiOrigin <value> --project <value> [--json] [--inlineIdentityJson <value>] [--authToken
<value>] [--site <value>]
FLAGS
--apiOrigin=<value> (required) [default: https://tilda.net, env: TILDA_CLI_API_ORIGIN] API origin
--authToken=<value> [env: TILDA_CLI_AUTH_TOKEN] Private key config. Must be of type { privateKey: string,
keyId: number } encoded in base64
--inlineIdentityJson=<value> [env: TILDA_CLI_INLINE_IDENTITY_JSON] Private key config. Must be of type { privateKey:
string, keyId: number }
--project=<value> (required) Project slug
--site=<value> Site slug
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Create a deployment keySee code: src/commands/deployment-key/create/index.ts
tilda help [COMMAND]
Display help for tilda.
USAGE
$ tilda help [COMMAND...] [-n]
ARGUMENTS
[COMMAND...] Command to show help for.
FLAGS
-n, --nested-commands Include all nested commands in the output.
DESCRIPTION
Display help for tilda.See code: @oclif/plugin-help
tilda login
Log in to Tilda
USAGE
$ tilda login --apiOrigin <value> [--json] [--inlineIdentityJson <value>] [--authToken <value>]
FLAGS
--apiOrigin=<value> (required) [default: https://tilda.net, env: TILDA_CLI_API_ORIGIN] API origin
--authToken=<value> [env: TILDA_CLI_AUTH_TOKEN] Private key config. Must be of type { privateKey: string,
keyId: number } encoded in base64
--inlineIdentityJson=<value> [env: TILDA_CLI_INLINE_IDENTITY_JSON] Private key config. Must be of type { privateKey:
string, keyId: number }
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Log in to TildaSee code: src/commands/login/index.ts
tilda logout
Log in to Tilda
USAGE
$ tilda logout --apiOrigin <value> [--json] [--inlineIdentityJson <value>] [--authToken <value>] [--force]
FLAGS
--apiOrigin=<value> (required) [default: https://tilda.net, env: TILDA_CLI_API_ORIGIN] API origin
--authToken=<value> [env: TILDA_CLI_AUTH_TOKEN] Private key config. Must be of type { privateKey: string,
keyId: number } encoded in base64
--force Force logout
--inlineIdentityJson=<value> [env: TILDA_CLI_INLINE_IDENTITY_JSON] Private key config. Must be of type { privateKey:
string, keyId: number }
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Log in to TildaSee code: src/commands/logout/index.ts
tilda plugins
List installed plugins.
USAGE
$ tilda plugins [--json] [--core]
FLAGS
--core Show core plugins.
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
List installed plugins.
EXAMPLES
$ tilda pluginsSee code: @oclif/plugin-plugins
tilda plugins add PLUGIN
Installs a plugin into tilda.
USAGE
$ tilda plugins add PLUGIN... [--json] [-f] [-h] [-s | -v]
ARGUMENTS
PLUGIN... Plugin to install.
FLAGS
-f, --force Force npm to fetch remote resources even if a local copy exists on disk.
-h, --help Show CLI help.
-s, --silent Silences npm output.
-v, --verbose Show verbose npm output.
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Installs a plugin into tilda.
Uses npm to install plugins.
Installation of a user-installed plugin will override a core plugin.
Use the TILDA_NPM_LOG_LEVEL environment variable to set the npm loglevel.
Use the TILDA_NPM_REGISTRY environment variable to set the npm registry.
ALIASES
$ tilda plugins add
EXAMPLES
Install a plugin from npm registry.
$ tilda plugins add myplugin
Install a plugin from a github url.
$ tilda plugins add https://github.com/someuser/someplugin
Install a plugin from a github slug.
$ tilda plugins add someuser/someplugintilda plugins:inspect PLUGIN...
Displays installation properties of a plugin.
USAGE
$ tilda plugins inspect PLUGIN...
ARGUMENTS
PLUGIN... [default: .] Plugin to inspect.
FLAGS
-h, --help Show CLI help.
-v, --verbose
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Displays installation properties of a plugin.
EXAMPLES
$ tilda plugins inspect mypluginSee code: @oclif/plugin-plugins
tilda plugins install PLUGIN
Installs a plugin into tilda.
USAGE
$ tilda plugins install PLUGIN... [--json] [-f] [-h] [-s | -v]
ARGUMENTS
PLUGIN... Plugin to install.
FLAGS
-f, --force Force npm to fetch remote resources even if a local copy exists on disk.
-h, --help Show CLI help.
-s, --silent Silences npm output.
-v, --verbose Show verbose npm output.
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Installs a plugin into tilda.
Uses npm to install plugins.
Installation of a user-installed plugin will override a core plugin.
Use the TILDA_NPM_LOG_LEVEL environment variable to set the npm loglevel.
Use the TILDA_NPM_REGISTRY environment variable to set the npm registry.
ALIASES
$ tilda plugins add
EXAMPLES
Install a plugin from npm registry.
$ tilda plugins install myplugin
Install a plugin from a github url.
$ tilda plugins install https://github.com/someuser/someplugin
Install a plugin from a github slug.
$ tilda plugins install someuser/somepluginSee code: @oclif/plugin-plugins
tilda plugins link PATH
Links a plugin into the CLI for development.
USAGE
$ tilda plugins link PATH [-h] [--install] [-v]
ARGUMENTS
PATH [default: .] path to plugin
FLAGS
-h, --help Show CLI help.
-v, --verbose
--[no-]install Install dependencies after linking the plugin.
DESCRIPTION
Links a plugin into the CLI for development.
Installation of a linked plugin will override a user-installed or core plugin.
e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
command will override the user-installed or core plugin implementation. This is useful for development work.
EXAMPLES
$ tilda plugins link mypluginSee code: @oclif/plugin-plugins
tilda plugins remove [PLUGIN]
Removes a plugin from the CLI.
USAGE
$ tilda plugins remove [PLUGIN...] [-h] [-v]
ARGUMENTS
[PLUGIN...] plugin to uninstall
FLAGS
-h, --help Show CLI help.
-v, --verbose
DESCRIPTION
Removes a plugin from the CLI.
ALIASES
$ tilda plugins unlink
$ tilda plugins remove
EXAMPLES
$ tilda plugins remove myplugintilda plugins reset
Remove all user-installed and linked plugins.
USAGE
$ tilda plugins reset [--hard] [--reinstall]
FLAGS
--hard Delete node_modules and package manager related files in addition to uninstalling plugins.
--reinstall Reinstall all plugins after uninstalling.See code: @oclif/plugin-plugins
tilda plugins uninstall [PLUGIN]
Removes a plugin from the CLI.
USAGE
$ tilda plugins uninstall [PLUGIN...] [-h] [-v]
ARGUMENTS
[PLUGIN...] plugin to uninstall
FLAGS
-h, --help Show CLI help.
-v, --verbose
DESCRIPTION
Removes a plugin from the CLI.
ALIASES
$ tilda plugins unlink
$ tilda plugins remove
EXAMPLES
$ tilda plugins uninstall mypluginSee code: @oclif/plugin-plugins
tilda plugins unlink [PLUGIN]
Removes a plugin from the CLI.
USAGE
$ tilda plugins unlink [PLUGIN...] [-h] [-v]
ARGUMENTS
[PLUGIN...] plugin to uninstall
FLAGS
-h, --help Show CLI help.
-v, --verbose
DESCRIPTION
Removes a plugin from the CLI.
ALIASES
$ tilda plugins unlink
$ tilda plugins remove
EXAMPLES
$ tilda plugins unlink myplugintilda plugins update
Update installed plugins.
USAGE
$ tilda plugins update [-h] [-v]
FLAGS
-h, --help Show CLI help.
-v, --verbose
DESCRIPTION
Update installed plugins.See code: @oclif/plugin-plugins
