@fly/cli
v0.56.2
Published
fly cli
Downloads
173
Readme
Fly cli
flyjs apps
flyjs apps:create
flyjs apps:delete
flyjs apps:move
flyjs build [PATH]
flyjs deploy [PATH]
flyjs help [COMMAND]
flyjs hostnames
flyjs hostnames:add HOSTNAME
flyjs login
flyjs logs
flyjs new NAME
flyjs orgs
flyjs releases
flyjs secrets
flyjs secrets:set KEY [VALUE]
flyjs server [PATH]
flyjs test [PATTERN]
flyjs apps
list your apps
USAGE
$ flyjs apps
OPTIONS
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/apps/index.js
flyjs apps:create
create a new app
USAGE
$ flyjs apps:create
OPTIONS
-a, --app=app The app to run commands against
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/apps/create.js
flyjs apps:delete
delete an app
USAGE
$ flyjs apps:delete
OPTIONS
-a, --app=app The app to run commands against
--env=env [default: production] environment to use for commands
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/apps/delete.js
flyjs apps:move
move an new app to another organization
USAGE
$ flyjs apps:move
OPTIONS
-a, --app=app The app to run commands against
--env=env [default: production] environment to use for commands
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/apps/move.js
flyjs build [PATH]
Build your local Fly app
USAGE
$ flyjs build [PATH]
ARGUMENTS
PATH [default: .] path to app
OPTIONS
-a, --app=app The app to run commands against
-o, --output=output (required) [default: .fly/release.tar.gz] Path to output file
--env=env [default: production] environment to use for commands
See code: lib/commands/build.js
flyjs deploy [PATH]
Deploy your local Fly app
USAGE
$ flyjs deploy [PATH]
ARGUMENTS
PATH [default: /home/vsts/work/1/s/packages/cli] path to app
OPTIONS
-a, --app=app The app to run commands against
--env=env [default: production] environment to use for commands
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/deploy.js
flyjs help [COMMAND]
display help for flyjs
USAGE
$ flyjs help [COMMAND]
ARGUMENTS
COMMAND command to show help for
OPTIONS
--all see all commands in CLI
See code: @oclif/plugin-help
flyjs hostnames
list hostnames for an app
USAGE
$ flyjs hostnames
OPTIONS
-a, --app=app The app to run commands against
--env=env [default: production] environment to use for commands
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/hostnames/index.js
flyjs hostnames:add HOSTNAME
add hostnames to an app
USAGE
$ flyjs hostnames:add HOSTNAME
ARGUMENTS
HOSTNAME hostname to add
OPTIONS
-a, --app=app The app to run commands against
--env=env [default: production] environment to use for commands
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/hostnames/add.js
flyjs login
login to fly
USAGE
$ flyjs login
See code: lib/commands/login.js
flyjs logs
logs for an app
USAGE
$ flyjs logs
OPTIONS
-a, --app=app The app to run commands against
-i, --instance=instance Instance ID to filter
-r, --region=region Region to filter
--env=env [default: production] environment to use for commands
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/logs.js
flyjs new NAME
create a new app
USAGE
$ flyjs new NAME
ARGUMENTS
NAME app-name
OPTIONS
-t, --template=template the template to use
See code: lib/commands/new.js
flyjs orgs
list your organizations
USAGE
$ flyjs orgs
OPTIONS
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/orgs.js
flyjs releases
list releases for an app
USAGE
$ flyjs releases
OPTIONS
-a, --app=app The app to run commands against
--env=env [default: production] environment to use for commands
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/releases.js
flyjs secrets
manage app secrets
USAGE
$ flyjs secrets
See code: lib/commands/secrets/index.js
flyjs secrets:set KEY [VALUE]
add secrets to an app
USAGE
$ flyjs secrets:set KEY [VALUE]
ARGUMENTS
KEY name of the secret
VALUE value of the secret
OPTIONS
-a, --app=app The app to run commands against
--env=env [default: production] environment to use for commands
--from-file=from-file use a file's contents as the secret value
--token=token The api token to use. This will override the token created with `fly login` if present.
See code: lib/commands/secrets/set.js
flyjs server [PATH]
run the local fly development server
USAGE
$ flyjs server [PATH]
ARGUMENTS
PATH [default: /home/vsts/work/1/s/packages/cli] path to app
OPTIONS
-p, --port=port [default: 3000] Port to bind to
--env=env [default: development] environment to use for commands
--inspect use the v8 inspector on your fly app
--uglify uglify your code like we'll use in production (warning: slow!)
--[no-]watch reload when source or configs change
See code: lib/commands/server.js
flyjs test [PATTERN]
run unit tests
USAGE
$ flyjs test [PATTERN]
ARGUMENTS
PATTERN [default: {test,spec,tests,specs}/**/*.{test,spec}.{js,ts}] test file path pattern
EXAMPLES
fly test test/**
fly test __test__/test_file.ts
fly test test/test_a.ts test/test_b.ts
fly test test/these/** !but_not_this.js
See code: lib/commands/test.js