@fly/cli

Fly cli

• fly apps
• fly apps:create
• fly apps:delete
• fly apps:move
• fly build [PATH]
• fly deploy [PATH]
• fly help [COMMAND]
• fly hostnames
• fly hostnames:add HOSTNAME
• fly login
• fly logs
• fly new NAME
• fly orgs
• fly releases
• fly secrets
• fly secrets:set KEY [VALUE]
• fly server [PATH]
• fly test [PATTERN]

fly apps

list your apps

USAGE
  $ fly 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

fly apps:create

create a new app

USAGE
  $ fly 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

fly apps:delete

delete an app

USAGE
  $ fly 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

fly apps:move

move an new app to another organization

USAGE
  $ fly 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

fly build [PATH]

Build your local Fly app

USAGE
  $ fly 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

fly deploy [PATH]

Deploy your local Fly app

USAGE
  $ fly 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

fly help [COMMAND]

display help for fly

USAGE
  $ fly help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

fly hostnames

list hostnames for an app

USAGE
  $ fly 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

fly hostnames:add HOSTNAME

add hostnames to an app

USAGE
  $ fly 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

fly login

login to fly

USAGE
  $ fly login

See code: lib/commands/login.js

fly logs

logs for an app

USAGE
  $ fly 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

fly new NAME

create a new app

USAGE
  $ fly new NAME

ARGUMENTS
  NAME  app-name

OPTIONS
  -t, --template=template  the template to use

See code: lib/commands/new.js

fly orgs

list your organizations

USAGE
  $ fly 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

fly releases

list releases for an app

USAGE
  $ fly 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

fly secrets

manage app secrets

USAGE
  $ fly secrets

See code: lib/commands/secrets/index.js

fly secrets:set KEY [VALUE]

add secrets to an app

USAGE
  $ fly 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

fly server [PATH]

run the local fly development server

USAGE
  $ fly 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

fly test [PATTERN]

run unit tests

USAGE
  $ fly 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