Clever Cloud allows you to deploy any Meteor.js application. This page will explain how to set up your application to run it on our services.
Be sure your
.meteor folder is in your git repository.
Refer to Quickstart for more details on application creation via the console.
- Make sure you have clever-tools installed locally or follow our CLI getting started guide.
- In your code folder, do
clever create --type <type> <app-name> --region <zone> --org <org>where :
typeis the type of technology you rely on
app-namethe name you want for your application,
zonedeployment zone (
parfor Paris and
orgthe organization ID the application will be created under.
Refer to clever create for more details on application creation with Clever Tools.
- Go to the Clever Cloud console, and find the app you want to fine tune under it’s organization.
- Find the Environment variables menu and select it.
- In this menu, you will see a form with VARIABLE_NAME and variable value fields.
- Fill them with the desired values then select Add.
- Don’t forget to “Update Changes” at the end of the menu.
- Make sure you have clever-tools installed locally. Refer to our CLI getting started.
- In your code folder, do
clever env set <variable-name> <variable-value>
Refer to environment variables reference for more details on available environment variables on Clever Cloud.
You can of course create custom ones with the interface we just demonstrated, they will be available for your application.
To run your Meteor.js application you need a few mandatory environment variables:
MONGO_URL: this is the mongo uri you can find in your mongodb’s dashboard, it has to start with
ROOT_URL: this is your application’s root url. It has to start with
PORT: keep the current value of 8080
With Meteor 2.6.n comes MongoDB 5.n and the new npm driver. You need to append
?directConnection=true in your
MONGO_URL to avoid the new mongo driver Service Discovery feature.
Some application require a
settings.json file to store api keys and other various private and public Meteor variables.
You can declare a
METEOR_SETTINGS environment variable and past the content of the json file as the value of this key.
Since building with the latest version of Node.js might fail, you should specify in the
package.json file of the application the version needed for your Meteor application ; as shown in Deploying Node.js apps documentation.
To find out which version is required by your application type the following command
meteor node -v inside root folder.
Currently with Meteor 2.6.1 the Node.js version is 14.18.3 so you should add the following inside the
You may change the node version value according to the application requirements.
Meteor.js uses a lot of memory during the build. You most likely will need to activate the dedicated build feature and set your vertical scaling size at least to M.
If your build still fails after you enabled the feature, please contact us on the support so we can set you a bigger scaler.
You can use the force-ssl atmosphere package to redirect your users to the HTTPS version of your application.
If you want to set custom start parameters, the main entry point of built meteor applications is:
Add in the
scripts.start field of the package.json:
node .build/bundle/main.js <parameters>
At each deployment, the needed Meteor.js version will be read from
.meteor/release and installed.
Your application will then be built using
meteor build --server-only and deployed from the files created by this command.
Clever Cloud injects environment variables from your application settings as mentioned in setting up environment variables and is also injecting in your application production environment, those from your linked add-ons.
On Clever Cloud you can define some build configuration: like the app folder to deploy or the path to validate your application deployment is ready To do that follow the documentation here and add the environement variable you need.
You need Git on your computer to deploy via this tool. Here is the official website of Git to get more information: git-scm.com
The “Information” page of your app gives you your Git deployment URL, it looks like this:
- Copy it in your clipboard
Locally, under your code folder, type in
git initto set up a new git repository or skip this step if you already have one
Add the deploy URL with
git remote add <name> <your-git-deployment-url>
Add your files via
git add <files path>and commit them via
git commit -m <your commit message>
Now push your application on Clever Cloud with
git push <name> master
Refer to git deployments for more details.
By linking an application to an add-on, the application has the add-on environment variables in its own environment by default.
Many add-ons do exist on Clever Cloud: refer to the full list and check add-ons dedicated pages for full instructions.
During add-on creation, an Applications screen appears, with a list of your applications. You can toggle the button to Link and click next. If you finish the process of add-on creation, the application is automatically linked to it.
In the Clever Cloud console, under the Service Dependencies menu of your application, you can use the Link add-ons dropdown menu to select the name of the add-on you want to link and use the add button to finish the process.
You can also link another application from the same page in the Clever Cloud console, using the Link applications dropdown menu.
Oplog tailing is supported on dedicated databases (starting from Hazelnut size). Contact the support to enable oplog. Once enabled, set the following environment variable:
Since Meteor 2.6.n the mongo driver detect the
MONGO_OPLOG_URL by itself and you should not add this to your environment variables.
If you want to migrate from your classic node.js app to a meteor application, contact our support in the console or at email@example.com with the application id.
Need more configuration? To run a script at the end of your deployment? To add your private SSH key to access private dependencies?
Go check the Common configuration page.
You may want to have an advanced usage of your application, in which case we recommend you to read the Administrate documentation section.
If you can’t find something or have a specific need like using a non supported version of a particular software, please reach out to the support.
The healthcheck allows you to limit downtimes. Indeed, you can provide us with paths to check. If these paths return something other than 200, we will consider the deployment as failed.
All you need is add one (or several) environment variable as such:
The deployment process will check all given paths. All of them must reply with a
200 OK response code.
Using the path listed above, below are the expected logs:
Response from GET /my/awesome/path is 200
Response from GET /my/other/path is 500
Health check failed:
- GET /my/other/path returned 500.
If the deployment fails after this message, please update your configuration and redeploy.
In this example, the 1st path is OK, but the 2nd one failed. This give you a hint on what failed in your application.
To make the most of a healthcheck endpoint, you should have it check your critical dependencies. For example:
SELECT 1 + 1;on your database
- retrieve a specific Cellar file
- ping a specific IP through a VPN
Did this documentation help you ?