You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've successfully got it running on an AWS machine, with vips and everything.
I did a npm i -g image-resizer
followed by a, mkdir resizer and image-resizer new into that directory.
Changing the variables in the .env file and then running gulp watch is working perfect.
But I wish to keep it running on production mode with pm2, but for some reason, when I set my machine's environment variable to NODE_ENV=production and then run node index.js from within that directory, there is no response. It just stays there and I'm getting no response on the expected PORT.
The text was updated successfully, but these errors were encountered:
Got it working.
Apparently my environment file wasn't being accepted. I then injected env variables from that env() function call directly. Worked perfectly then.
Instead of injecting the env(), you can change the 'watch' to 'default', so you can do "pm2 start -n image_server gulp" and it'll fetch the .env file and scaffold out the server for you
I've successfully got it running on an AWS machine, with vips and everything.
I did a
npm i -g image-resizer
followed by a,
mkdir resizer
andimage-resizer new
into that directory.Changing the variables in the
.env
file and then runninggulp watch
is working perfect.But I wish to keep it running on
production
mode with pm2, but for some reason, when I set my machine's environment variable toNODE_ENV=production
and then runnode index.js
from within that directory, there is no response. It just stays there and I'm getting no response on the expected PORT.The text was updated successfully, but these errors were encountered: