I am not able to understand why pm2 starts my ghost blog in developement instead of production.
I can run this
npm start --production and everything is fine like I want it. But if I try to use pm2
pm2 start index.js it starts my blog in developement which I don't want to. I must be blind but can not see in the docs how I can force pm2 to start in production mode.
I only have success starting the app with npm like this:
npm start --production
I tried with a config file ecosystem.config.js and to start it like this:
pm2 start ecosystem.config.js or
pm2 start ecosystem.config.js --env production but it seems to start in developement. Here is my config file.
module.exports = {
apps : [
{
name : "asle",
script : "index.js",
env: {
COMMON_VARIABLE: "true"
},
env_production : {
NODE_ENV: "production"
}
}
]
}
Because ghost blog always runs in development mode by default. If you want to run it with pm2 in production use following command
NODE_ENV=production pm2 start index.js
You can also read in my blog post: https://drifts.io/how-to-setup-ghost-blog-on-vps/#step5installpm2processmanager
Also dont forget to use pm2 startup and save to make sure it persistent over reboots.
Have you tried to create an ecosystem file to declare how you want to launch in production ?
http://pm2.keymetrics.io/docs/usage/application-declaration/
If yes can you show it ?
Related
I have a vue3 + vitejs application that I would like to deploy on windows with pm2.
When I run the npm start myapp command, the status is in error.
Can you help me please?
ecosystem.config.js
name: 'myapp',
cwd: 'C:\myapp',
script: 'npm',
args: 'run dev'
Thank you.
What's the error. Secondly, you shouldn't be deploying your application through PM2. PM2 is normally used for backend node services. You're better off using IIS if you're on windows, building the application npm run build, and pointing IIS to the dist folder.
pm2 start verdaccio failed, the status is stopped.
$ npm i -g pm2 verdaccio
$ pm2 start verdaccio
I've have been running verdaccio in pm2 for 1 year by know and I use this after installing it globally via npm.
Start
pm2 start `which verdaccio`
Restart
pm2 restart verdaccio
And that works pretty well for me.
The problem is pm2 finding verdaccio in the first place. That's why using which solves it, but that is not always possible in Windows.
I've managed to run verdaccio in pm2 on Windows, without even installing it globally (so that I could commit my configs, plugin packages, etc), with this:
// ecosystem.config.js
module.exports = {
apps : [{
name: 'verdaccio',
script: './node_modules/verdaccio/build/lib/cli', // local package, that pm2 can run with "node <script>"
args : '--config ./config.yaml', // local confis
node_args: '-r esm', // verdaccio's package didn't contain "type": "module"
exec_mode: 'fork' // verdaccio does not currently support PM2's cluster mode
}]
}
PS.: these are my dependencies:
// package.json
"dependencies": {
"esm": "^3.2.25",
"verdaccio": "^5.10.2",
"verdaccio-activedirectory": "^1.0.2",
"verdaccio-simplegroup": "^1.0.2"
},
for someone still stumbling upon this problem. you can try deleting the process then starting it again. I solved it this way.
I set up pm2 with a watch, so each time a git pull is done, it auto reloads the app.
This works, unless the app dependencies have changed, then it needs to run npm install first. This causes pm2 to restart and crash over and over until the install is done.
Is there a way to have pm2 watch automatically run npm install before restarting?
there is no way but, you can add script in package.json
...
scripts: {
....
"postinstall" "pm2 restart (your process id from pm2)"
}
...
Run pm2 start (your entry file server) and get process id.
Always run npm install and then pm2 will restart process after that
Note that you need to install pm2 globally using "npm i -g pm2" on the machine
I'm using Gulp to compile and minify SCSS, Pug, JSX and that sort of things. So in the development process as usual I'm opening the terminal window and typing gulp and it watches my files. But I have to keep open the terminal window and Gulp tab, otherwise my files don't be compiled.
I'm using PM2 too. When I wanna start a Node job I just write pm2 start file.js --watch and pm2 startup in order to start the script on operating system opening. I wanna do the same thing for Gulp. I've tried like pm2 start gulpfile.js --watch, but it doesn't work.
How can I use Gulp with PM2?
I am no expert in gulp, but you can execute your gulp command via pm2 by defining it in the process file at your project root.
ecosystem.json
{
"apps": [
{
"name": <name_of_your_app>,
"script": "gulp"
}
]
}
Then, from terminal, run $ pm2 start ecosystem.json. You can also define watch options at that process file. See this for more details.
I'v made a static single page site using grunt. I'm now trying to deploy it to heroku using the heroku-buildpack-nodejs-grunt for node grunt.
Below is a pic of my root directory:
Here's my Gruntfile package.json:
Procfile:
web: node index.html
When I run $ git push heroku master it gets to the Gruntfile and fails:
-----> Found Gruntfile, running grunt heroku:production task
>> Local Npm module "grunt-contrib-uglify" not found. Is it installed?
The above errors proceed to list all local NPM modules as not found. If I list all loadNpmTasks instead of using "load-grunt-tasks", I get the exact same error.
When I $ heroku logs I get:
Starting process with command `node web.js`
Error: Cannot find module '/app/web.js'
Can anyone see where I've gone wrong?
For anyone passing by here, I wasn't able to solve the problem. This is where I got to:
In my Gruntfile, I moved npm modules from devDependencies to dependencies. Heroku was then able to install these dependencies.
However, when Heroku ran the tasks, it stops at the haml task w/ error "You need to have Ruby and Haml installed and in your PATH for this task to work". Adding ruby & haml to the Gruntfile as engines did not work.
The only thing I can think of is that maybe Heroku installs your devDependencies first, tries to run Grunt, but since it didn't install load-grunt-tasks yet, you don't get the grunt.loadNpmTasks( 'grunt-contrib-uglify' ); line (which load-grunt-tasks does for you), and thus Grunt can't find the package.
Can you try changing your Gruntfile to explicitly list out all npm modules using the grunt.loadNpmTasks() method?
EDIT:
Just remembered another thing I had to do:
heroku labs:enable user-env-compile -a myapp
heroku config:set NODE_ENV=production
(Obviously replacing myapp with your Heroku app name.)
This makes Heroku allow user set environment variables and then sets your server to production. Try that, and set your dependencies and devDependencies as you had them originally (just to see if it works).
I am coming pretty late to the game here but I have used a couple methods and thought I would share.
Option 1: Get Heroku to Build
This is not my favorite method because it can take a long time but here it is anyway.
Heroku runs npm install --production when it receives your pushed changes. This only installs the production dependencies.
You don't have to change your environment variables to install your dev dependencies. npm install has a --dev switch to allow you to do that.
npm install --dev
Heroku provides an article on how you can customize your build. Essentially, you can run the above command as a postinstall script in your package.json.
"scripts": {
"start": "node index.js",
"postinstall": "npm install --dev && grunt build"
}
I think this is cleaner than putting dev dependencies in my production section or changing the environment variables back and forth to get my dependencies to build.
Also, I don't use a Procfile. Heroku can run your application by calling npm start (at least it can now almost two years after the OP). So as long as you provide that script (as seen above) Heroku should be able to start your app.
As far as your ruby dependency, I haven't attempted to install a ruby gem in my node apps on Heroku but this SO answer suggests that you use multi buildpack.
Option 2: Deploy Your Dependencies
Some argue that having Heroku build your application is bad form. They suggest that you should push up all of your dependencies. If you are like me and hate the idea of checking in your node_modules directory then you could create a new branch where you force add the node_modules directory and then deploy that branch. In git this looks like:
git checkout -b deploy
git add -f node_modules/
git commit -m "heroku deploy"
git push heroku --force deploy:master
git checkout master
git branch -D deploy
You could obviously make this into a script so that you don't have to type that every time.
Option 3: Do It All Yourself
This is my new favorite way to deploy. Heroku has added support for slug deploys. The previous link is a good read and I highly recommend it. I do this in my automated build from Travis-CI. I have some custom scripts to tar my app and push the slug to Heroku and its fast.
I faced a similar problem with Heroku not installing all of my dependencies, while I had no issue locally. I fixed it by running
heroku config:set USE_NPM_INSTALL=true
into the path, where I deployed my project from. This instructs Heroku to install your dependencies using npm install instead of npm ci, which is the default! From Heroku dev center:
"Heroku uses the lockfiles, either the package-lock.json or yarn.lock, to install the expected dependency tree, so be sure to check those files into git to ensure the same dependency versions across environments. If you are using npm, Heroku will use npm ci to set up the build environment."