Skip to content

Comment on Meteor in Productionparent

Comments

I don't get it. There is the "meteor bundle" command, which as far as I can tell does the exact same thing. "meteor bundle" turns your Meteor app into a regular Node.js app. It does not bundle Node.js itself and it does not bundle MongoDB.

The author mentioned that Demeteorizer allows a Meteor app to be able to run on any Node.js hosting provider. "meteor bundle" does that too. In last week's announcement about the Phusion Passenger app server + Meteor support, I documented how one can use Meteor bundles with Passenger. If you look at the instructions[1] you'll see that the instructions for deploying a Meteor bundle are the same as deploying a Node.js app.

So how is Demeteorizer different from "meteor bundle"?

[1] http://tinyurl.com/mj9ex3y

Demeteorizer uses "meteor bundle" internally. What it does differently is generate a package.json file from all of those bundled dependencies. It fixes the case where your development platform is different than your production platform. The native modules need to be recompiled. Using a package.json and npm install makes that really easy. Checkout the big red text in the Meteor docs on deploying[1].

[1] http://docs.meteor.com/#deploying

I never did get Demeteorizer to work so I can't compare them but yes the meteor bundle command gives you a Node.js app that can be deployed like any other.

As I understand it the former was created before the meteor bundle command was available.

I'm the author of Demeteorizer. Would love to hear what happened so we can get it fixed.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.