Say hello to a more convenient way to deploy your app. With just a few clicks, you can update or deploy your app directly from your repository, available for all plans including the free plan.
An easier way to deploy your apps.
Over the last few months, we’ve been working hard to bring you Meteor Cloud’s newest feature, Push to Deploy! This feature has been in Meteor’s roadmap for a while, and we’re very excited to share this update with you.
After reading this blog, you won’t need to have a machine anymore to run meteor deploy because you can now deploy changes to your app just by pushing changes to a branch on GitHub. You can also create new apps on Cloud by using the UI and a few clicks to select the GitHub repository you want to publish. Let’s dive right in!
Where to start?
To get started with Push to Deploy, all you need to do is follow three basic steps, and you’ll have a new app deployed or an existing app configured with Push to Deploy.
Our current integration is just with GitHub, but we’re planning to add more Git providers in the future. For now, you need to have a GitHub repository with a Meteor project in it. Here is a list of Meteor versions that support this feature: 1.12.2, 2.0.1, 2.1.2, 2.2.4, 2.3.7, and any version from 2.4.1 to the latest.
How to use Push to Deploy?
In this section, we’ll show you how to easily set up Push to Deploy for your new app. If you want to configure an existing app, skip this section and scroll down to Setting up Push to Deploy for Existing Apps.
First, go to your Cloud account by clicking here. Then go to APPS > DEPLOY A NEW APP. After clicking the button, you’ll be brought to this page.
Configure Push to Deploy on Meteor Cloud.
In this step, you need to choose your account from the Git provider and then choose the repository with the Meteor app you want to deploy.
New app configuration: choose an account and repository.
The last step is to configure the last details. Starting with the Account field, followed by the Plan, Container Size, and then Region. In the next section, Deploy Options, you’ll be able to choose which branch you’ll use as your deploy branch. Note that every commit done on this branch will trigger a deploy. In addition, you can also opt to use or not use our shared MongoDB Cluster.
You can also use the Advanced Options section. Fields include Meteor Settings, Root Directory, Pre Deploy Command, Deploy Arguments, Build Container RAM, and Environment Variables.
Deploy options and Advanced options for your app.
Setting up Push to Deploy for Existing Apps
Go to the app page in cloud.meteor.com, choose the app you want to be configured with Push to Deploy, and then you’ll be brought to the app details page. Next, click the SET UP PUSH TO DEPLOY button.
Set up push to deploy with an existing app.
Basically, the first two steps are the same as deploying a new app. You’ll just have to connect your Git provider and then choose the repository. For the last step, you’ll have a few options to change since the app is already deployed and all the other fields are already defined. You just need to make sure everything is correct in the Deploy Options section.
That’s it! You’re all done. If you want to edit the details again, click the CONFIGURE PUSH TO DEPLOY button on the app details page.
One last thing to note on Galaxy is the Next Auto Deploy Settings which is located in the app version tab. You can use this field to add app settings for the next deploy. When you commit to the branch you configured, these settings will be used every time for the next deploys. If you don’t want to use it anymore, leave the field empty.
Next auto deploy settings (Galaxy). Leave it empty if you don’t want to use it.
We can’t wait for you to try this new feature of ours and we’re grateful for an amazing community around us that uses Meteor. If you have any questions, concerns, or feedback, please feel free to reach out to us at [email protected].
Save time and reduce headaches, it’s time to use Push to Deploy!