Google uses cookies and data to:

Nothing in the Meteor guide is required to build a Meteor application—you can certainly use the platform in ways that contradict the principles and patterns of the guide. However, the guide is an attempt to document best practices and community conventions, so we hope that the majority of the Meteor community will benefit from adopting the.

Meteor is a powerful cinematic sound design tool for creating epic swells, powerful impacts and dramatic backdrops for film, games, trailers, music and more. Immerse your audience in a unique sonic environment through the 7-layer architecture and on-board modulations and effects, including a. Meteor is an open source platform, and you can run the apps that you make with Meteor anywhere just like regular Node.js applications. But operating Meteor apps correctly, so that your apps work for everyone, can be tricky if you are managing your infrastructure manually. This is why we recommend running production Meteor apps on Galaxy.

• Deliver and maintain services, like tracking outages and protecting against spam, fraud, and abuse
• Measure audience engagement and site statistics to understand how our services are used

If you agree, we’ll also use cookies and data to:

• Improve the quality of our services and develop new ones
• Deliver and measure the effectiveness of ads
• Show personalized content, depending on your settings
• Show personalized or generic ads, depending on your settings, on Google and across the web

For non-personalized content and ads, what you see may be influenced by things like the content you’re currently viewing and your location (ad serving is based on general location). Personalized content and ads can be based on those things and your activity like Google searches and videos you watch on YouTube. Personalized content and ads include things like more relevant results and recommendations, a customized YouTube homepage, and ads that are tailored to your interests.

Click “Customize” to review options, including controls to reject the use of cookies for personalization and information about browser-level controls to reject some or all cookies for other uses. You can also visit g.co/privacytools anytime.

On this page you will learn how you can deploy your app to a server that is running Passenger. You can either follow these instructions with your own app, or you can use the sample Meteor app we prepared.

1 Transferring the Meteor package to the server

1.1 Build package

To deploy your Meteor app to production, we need to create a packaged version of it. A packaged Meteor app contains the Meteor runtime and various other necessary things for running a Meteor app in production.

Meteoroids (animerrill Productions) Mac Os Catalina

In order to provide you appropriate instructions, please choose your Meteor version:

Inside your application's code directory, on your local computer, use the meteor bundlemeteor build command to create a Meteor package tarball.

Why create a package?

Wondering why we instruct you to create a package, instead of just using the Meteor app in unpackaged form? Learn more at About Meteor support.

'meteor bundle' deprecated?

Meteor will probably tell you that meteor bundle is deprecated in favor of meteor build. Please ignore that message, because for the purpose of running a Meteor web application on Passenger, only meteor bundle does what we want.

meteor bundle creates a packaged web application, in the form of a Node.js web app with the Meteor runtime included. meteor build is a more comprehensive tool that not only does what meteor bundle does, but also builds iOS and Android app packages. However, Passenger is a web application server, so iOS and Android packages are not relevant to us, which is why we recommend using meteor bundle instead of meteor build.

1.2 Upload package to the server

Copy the package to your production server, for example using scp:

Replace adminuser with the name of an account with administrator privileges or sudo privileges.

1.3 Login to your server, create a user for the app

Login to your server with SSH:

Replace adminuser with the name of an account with administrator privileges or sudo privileges.

Now that you have logged in, you should create an operating system user account for your app. For security reasons, it is a good idea to run each app under its own user account, in order to limit the damage that security vulnerabilities in the app can do. Passenger will automatically run your app under this user account as part of its user account sandboxing feature.

You should give the user account the same name as your app. But for demonstration purposes, this tutorial names the user account myappuser.

We also ensure that that user has your SSH key installed:

1.4 Extract package

You need extract the package to a permanent location on the server. A good location is /var/www/APP_NAME. Let us create that directory.

Replace myapp and myappuser with your app's name and your app user account's name.

Now let us extract the package:

Your extract app package directory now lives on the server at /var/www/myapp/bundle.

2 Preparing the app's environment

2.1 Install MongoDB

During development, the Meteor runtime takes care of starting MongoDB for you. MongoDB is the database engine that Meteor uses. But a packaged Meteor app does not start MongoDB for you. Instead, a packaged Meteor app expects that MongoDB is already running somewhere, and that you tell the app where that MongoDB instance is.

2.2 Login as the app's user

All subsequent instructions must be run under the application's user account. While logged into your server, login under the application's user account as follows:

2.3 Install app dependencies

Your application has various dependencies.They must be installed. Most of these dependencies are Javascript libraries, managed by npm. You can install them by running npm install in your app's package directory, under the programs/server subdirectory:

Your app may also depend on services, such as Redis etc. With the exception of MongoDB, installing services that your app depends on is outside of this tutorial's scope.

3 Configuring Apache and Passenger

Now that you are done with transferring your app's code to the server and setting up an environment for your app, it is time to configure Apache so that Passenger knows how to serve your app.

3.1 Go back to the admin account

You have previously logged into your app's user account in order to prepare the app's environment. That user does not have sudo access. In the next steps, you need to edit configuration files, for which sudo access is needed. So you need to switch back to the admin account.

This can be done by simply exiting the shell that was logged into the app's user account. You will then be dropped back to the admin account. For example:

3.2 Edit Apache configuration file

Meteoroids (animerrill Productions) Mac Os X

We need to edit your Apache configuration file and setup a virtual host entry that points to your app. This virtual host entry tells Apache (and Passenger) where your app is located.

Open your Apache configuration file. For example:

Don't know where your Apache configuration file is? Read Working with the Apache configuration file.

Let us add a virtual host entry at the end of that file. At the end of the file, insert:

Replace yourserver.com with your server's host name and replace /var/www/myapp/bundle with your application's package directory path. Replace myappdb with an appropriate MongoDB database name. Also be sure to set ROOT_URL to an appropriate value.

When you are done, restart Apache:

(Depending on your operating system, the right command may be apache2ctl instead of apachectl.)

3.3 Test drive

You should now be able to access your app through the server's host name! Try running this from your local computer. Replace yourserver.com with your server's hostname, exactly as it appears in the Apache config file's ServerName directive.

If you do not see your app's front page HTML, then these are the most likely causes:

1. You did not correctly configure your ServerName directive. The ServerName must exactly match the host name in the URL. For example, if you use the command curl http://45.55.91.235/ to access your app, then the ServerName must be 45.55.91.235.
2. You did not setup DNS records. Setting up DNS is outside the scope of this tutorial. In the mean time, we recommend that you use your server's IP address as the server name.

Next step

Congratulations, you have successfully deployed your app!

Continue: Deploying updates »