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 have a project that utilizes the gm package to resize uploaded images on a Google Chrome kiosk web app. Gm does this by running GraphicsMagick via cross-spawn.
This is working as expected when I use node server.js, but when I run it via forever server.js the child processes instantiated by gm come to the foreground for a couple of milliseconds before closing again. Is there any way to prevent this behavior and have them be invisible or open in the background?
Windows 10
Node@6.6.0
Forever@0.15.3
gm@1.23.1
The text was updated successfully, but these errors were encountered:
I have a project that utilizes the gm package to resize uploaded images on a Google Chrome kiosk web app. Gm does this by running GraphicsMagick via cross-spawn.
This is working as expected when I use
node server.js
, but when I run it viaforever server.js
the child processes instantiated by gm come to the foreground for a couple of milliseconds before closing again. Is there any way to prevent this behavior and have them be invisible or open in the background?Windows 10
Node@6.6.0
Forever@0.15.3
gm@1.23.1
The text was updated successfully, but these errors were encountered: