meteor deploy <site>
Deploys the project in your current directory to Meteor's servers
Arguments
Name | Description |
---|
site | You can deploy to any available name under "meteorapp.com" without any additional configuration, for example, "myapp.meteorapp.com". If you deploy to a custom domain, such as "myapp.mydomain.com", then you'll also need to configure your domain's DNS records. See the Meteor / Galaxy docs (http://cloud-guide.meteor.com/dns.html) for details |
Options
Name | Description |
---|
--delete, -D | Permanently delete this deployment |
--debug | Deploy in debug mode (don't minify, etc) |
--settings, -s <JSON File> | Set optional data for Meteor.settings |
--allow-incompatible-update | Allow packages in your project to be upgraded or downgraded to versions that are potentially incompatible with the current versions, if required to satisfy all package version constraints |
--deploy-polling-timeout <milliseconds> | The number of milliseconds to wait for build/deploy success or failure after a successful upload of your app's minified code; defaults to 15 minutes |
--no-wait | Exits when Meteor has uploaded the app's code instead of waiting for the deploy to conclude |
--cache-build | Reuses the build already created if the git commit hash is the same |
--free | When deploying an app for the first time, you can pass this option to deploy your app in the Galaxy's free mode |
--plan | You can change the app plan by providing this argument with one of the following values: professional, essentials, or free. Be aware that this argument overwrites the `--free` argument |
--mongo <true/false> | If this flag is true and it's not provided a mongo url in the settings ('galaxy.meteor.com'.env.MONGO_URL), when deploying, Galaxy will create a database to your app in its shared cluster and will insert the URL in your app's settings for you |
--container-size <size> | Change your app's container size using the deploy command |