Please write a tutorial on how to take the MERN scaffolding to a cloud server and DB?

I have been using MEANJS.org and it's really wonderful. So many features and it's easy to work with, well documented.

For MERN, I have been disappointed, because I am simply trying to containerize it and put it in the cloud; I fail over and over.

I am a newbie but it should be really easy to do this: a) Change the port to 80 in config.js b) Change the DB to point to another remote end point c) Run with remote DB, without sudo on a Mac

If I attempt to "npm start" without sudo, and I have a remote end point for DB, npm start fails. What is a solution to this? I do not believe a remote cloud provider is going to allow me sudo..

If I attempt to change the server port to 80, even locally with sudo npm start, the app fails.

This scaffolding at this point is very brittle, and if I attempt to change the env in small ways, it fails.

Can we please have a tutorial that explains exactly what needs to change, in order to start the app without sudo (with remote DB), and change to the normal HTTP port?

EDIT: I would also like to say that I am simply attempting the following:

a) Use Mongolabs.com free DB instead of local mongodb b) Use bluemix.net free app container hosting via their blumix CLI and push my local running MERN app to the cloud, which is usually very easy to do

If we could focus on this, because I believe it is necessary for all developers to be able to do something very similar to this, and MERN is failing at this for me right now.

@surfyogi, You simply need to set MONGO_URL and PORT environment variables right. For you, change the start:prod npm script to something like this- "start:prod": "cross-env NODE_ENV=production MONGO_URL=foobar PORT=80 node index.js"

Replace value of MONGO_URL with whatever your remote URL for mongo is. That should be as simple as that. I hope you know that passing proper environment variables is a thing to consider before deploying anything in production. This is just that.

OK, that worked. But only if I have root access on my personal machine or sudo. If I edit the config.js instead, and set MONGO_URL and PORT there, then it fails to start, with the npm start script. How to start without npm and get rid of needed root authority? Not sure how to set the env vars, since it doesn't seem to work if I touch config.js.. can I set env vars in config.js and then use 'node index.js'? Please recommend a procedure to get away from npm, it seems to be what is requiring root access. thx, J-

@surfyogi You don't need to edit config.js to set env variables. You can do it like this MONGO_URL=<URL_HERE> npm run start:prod.

I think NPM is an issue here, when deploying to production, would root access be needed unless things are correctly setup for npm to not require root access? docs.npmjs.com/getting-started/fixing-npm-permiss… This article talks about how to make npm less needy for permissions, and in my case, I want to deploy to cloud with a PaaS container, and I don't have root access. So it seems we need a solution for how to make nmp work without root, and that means administration of npm is needed, as talked about in this article, 2 choices, and I don't know which is best. thx, Jeff.

Thread

Please write a tutorial on how to take the MERN scaffolding to a cloud server and DB?

Responses(1)

Recent threads

Search Hashnode

Please write a tutorial on how to take the MERN scaffolding to a cloud server and DB?

Responses(1)

Recent threads