> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help-legacy.galaxycloud.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Commands

**A reference for Galaxy's commands**

## meteor CLI: Frequently Used Commands

### deploy

#### Mac and Unix

`meteor deploy` can be used for creating new apps and updating existing ones.

The full command is:

```shell
DEPLOY_HOSTNAME=[region] meteor deploy [hostname] --settings [path-to-settings-file]
```

- `region` should be us-east-1.galaxy.meteor.com for the US region, eu-west-1.galaxy.meteor.com for the EU region or ap-southeast-2.galaxy.meteor.com for the Asia-Pacific region.
- `hostname` is the fully qualified domain name where you’re planning to host your application (for example, ‘www.facebook.com’).
- `path-to-settings-file` is the path to your JSON settings file (for example, ‘./settings.json’).

You don't have to specify `DEPLOY_HOSTNAME` if:

- your Meteor version is 1.3.3 or higher, and you are deploying to the US region
- your Meteor version is 1.3.3 or higher, you are deploying to the EU region and have already configured your hostname's DNS settings

If your app satisfies these conditions, the deployment command can be simplified to:

```shell
meteor deploy [hostname] --settings [path-to-settings-file]
```

#### Windows

On Windows, the deploy command should be split into two separate commands, occupying two separate lines.

`DEPLOY_HOSTNAME=...` should be changed to `SET DEPLOY_HOSTNAME...` and should occupy one line. `meteor deploy` should occupy another line.

You don't have to set `DEPLOY_HOSTNAME` if your app meets the conditions described above.

### authorized transfer

`meteor authorized` can be used to transfer applications with the `--transfer` flag.

- Transfer with Meteor 1.3 or higher versions:

```shell
DEPLOY_HOSTNAME=galaxy.meteor.com meteor authorized [your_existing_hostname] --transfer [new_account_name]
```

- Transfer with Meteor 1.2 or lower versions:

```shell
DEPLOY_HOSTNAME=galaxy.meteor.com meteor authorized [your_existing_hostname] --add [new_account_name]
```

For this to work, you must have deploy privileges to the account `new_account_name`.

### whoami

`meteor whoami` will tell you which user you are logged in as.

This can be important for troubleshooting, if you are a member of one or more organizations and are having access issues.

### login

`meteor login` will prompt you for a username and password to log you in, given the correct credentials.

### login with token

`METEOR_SESSION_FILE=[token-file] meteor login` will ask you for your username and password, then create a deployment token you can use to issue other commands, such as the deploy command.

This token will be good for 90 days from the time of generation.

- `token-file` is the path to your JSON deployment token file (for example, ‘./token.json’).

### logout

`meteor logout` will log you out as the current user.

### list sites

`meteor list-sites` lists all the apps you have access to, across all your organizations.

### update

`meteor update` allows you to update your Meteor version. You can use the `--release` flag to specify a version.

This can resolve issues involving deployment and application uptime, especially if the Meteor version used to deploy your app significantly predates the most recent Meteor version.