CODEWITHSUNDEEP
meteormodulus
oskare
oskare

Reputation: 1061

Package.json when deploying Meteor on Modulus

I'm trying to push an updated version of my Meteor app to Modulus after switching dev environment but I now get the following:

Client:

Unable to connect to any application instances.

Server:

Now using node v6.2.0
Found package.json: ./package.json
WARNING: Main file not specified in package.json.
WARNING: Looking for common main file names: index.js, app.js, server.js, main.js.
ERROR: No main or start script found. There is no application to run.

Before pushing this last update, the server log looked like below after successful startup but I'm not sure what the actual problem is. Any ideas?

Last functioning startup message on server:

Now using node v0.10.41
Found package.json: ./programs/server/package.json
Start script specified in package.json: node ../../main
Running command: npm start

> [email protected] start /mnt/app/programs/server
> node ../../main

Now using node v0.10.41
Found package.json: ./programs/server/package.json
Start script specified in package.json: node ../../main
Running command: npm start

Upvotes: 2

Views: 334

Answers (1)

ghybs
ghybs

Reputation: 53185

Just for the record, it depends on your modulus-CLI version:

  • With modulus-CLI version <= 5.x, you have to use a Modulus Node.js runtime. The modulus deploy command will demeteorize your Meteor project (essentially build it and modify a few parameters, including the package.json file, to specify the start script) and upload the resulting bundle to your Node instance.
  • With modulus-CLI version >= 6.0.0, you have to use a Modulus Meteor runtime. The modolus deploy command will directly upload your Meteor project source code (except what is specified in .modulusignore file), and the magic will happen on the build server Modulus side.

Upvotes: 2

Related Questions