Setup Node.js App<\/code> under Software<\/code>.<\/p>\n\n\n\n![\"\"](\"https:\/\/supporttest.hemsida.eu\/wp-content\/uploads\/2017\/10\/cpanel_icon_nodejs.png\")
<\/a><\/figure>\n\n\n\nOnce there, you can see all your existing Node.js applications, and also create a new one:<\/p>\n\n\n\n![\"\"\/](\"https:\/\/supporttest.hemsida.eu\/wp-content\/uploads\/2017\/10\/skapa_nodejs_app-1.png\")
<\/a><\/figure>\n\n\n\nAfter clicking the Create application<\/code> button, you get to adjust some settings for your app:<\/p>\n\n\n\n![\"\"](\"https:\/\/supporttest.hemsida.eu\/wp-content\/uploads\/2019\/10\/settings_for_node.js-app.png\")
<\/a><\/figure>\n\n\n\nThe six available options imply the following:<\/p>\n\n\n\n
\nNode.js version<\/code> – the version of Node.js you want to use.<\/li>\n\n\n\nApplication mode<\/code> – here you select if the app should be run in development or production mode.<\/li>\n\n\n\nApplication root<\/code> – the folder on the server where you’re going to upload the files for the Node.js application. Keep in mind that the application root shouldn’t be the same folder as the document root for the domain you use (below).<\/li>\n\n\n\nApplication URL<\/code> \u2013 the domain and URI where the app should be accessible. Leave it blank to run the application directly on the domain. To use a specific directory, enter \/directory<\/code>, e.g.<\/em> \/node-app<\/code> to make your application accessible via yourdomain.com\/node-app<\/code>.<\/li>\n\n\n\nApplication startup file<\/code> \u2013 unless you have a specific startup file for your app, you can leave this field empty. If the field is left blank, cPanel will create an app.js<\/code> file for you.<\/li>\n\n\n\nPassenger log file<\/code> – here you set a directory where you wish logs from the application to be saved.<\/li>\n<\/ul>\n\n\n\nOnce you’re done adjusting the settings, click Create<\/code>. Now a virtualenv<\/a><\/code> will be created where you can install Node.js packages for your application. A virtualenv<\/code> in the Node.js world can be described as a virtual environment where you can install packages that will not interfere with the system or with other virtualenv<\/code>s. Thus, it’s a way to separate your different Node.js environments. You can access a specific virtualenv<\/code> after logging on to your web hosting account via SSH. More information about connecting via SSH can be found here<\/a>.<\/p>\n\n\n\nAfter initial setup, you can see your new installation in the list of created Node.js applications.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/supporttest.hemsida.eu\/wp-content\/uploads\/2017\/10\/lista_over_node-appar.png\")
<\/a><\/figure>\n\n\n\nIf you click the pen icon, you will get access to the settings for the application:<\/p>\n\n\n\n![\"Inst\u00e4llningar](\"https:\/\/supporttest.hemsida.eu\/wp-content\/uploads\/2017\/10\/installningar_uppsatt_nodejs_app.png\")
<\/a><\/figure>\n\n\n\nHere, you will see information about the Node.js app that is set up, and you can also edit the settings.<\/p>\n\n\n\n
On top, you have a few buttons to manage your application:<\/p>\n\n\n\n
\nDestroy<\/code> \u2013 delete your application.<\/li>\n\n\n\nCancel<\/code> \u2013 discard changes and return to the list of applications.<\/li>\n\n\n\nSave<\/code> \u2013 save changes made to the application.<\/li>\n<\/ul>\n\n\n\nUnder the buttons, you’ll find Enter to the virtual environment<\/code>. This command can be copied and run via SSH to activate the virtual Node.js environment (virtualenv<\/code>) for your application. Please refer to the section above regarding virtualenv<\/code> and SSH access.<\/p>\n\n\n\nA bit further down, you’ll find more buttons:<\/p>\n\n\n\n
\nStop app<\/code> \u2013 stop the Node.js application. Will change to Start app<\/code> if the application is currently stopped.<\/li>\n\n\n\nRestart<\/code> \u2013 restart the application.<\/li>\n<\/ul>\n\n\n\nYou can also manage settings for your application:<\/p>\n\n\n\n
\nNode.js Version<\/code> \u2013 the chosen Node.js version.<\/li>\n<\/ul>\n\n\n\n\nApplication mode<\/code>,Application root,<\/code> Application URL<\/code>, Application startup file<\/code> samt Passenger log file<\/code> \u2013 please refer to the section above regarding these.<\/li>\n\n\n\nDetected configurations files<\/code> \u2013 here you may install various node packages via npm.<\/li>\n\n\n\nEnvironment variables<\/code> \u2013 here you may set various environment variables for your application.<\/li>\n<\/ul>\n\n\n\nVia SSH<\/h2>\n\n\n\n
You may also manage certain aspects of your Node.js application via SSH.<\/p>\n\n\n\n
Restart a Node.js application<\/h3>\n\n\n\n
To restart a Node.js application via SSH, begin by connecting to your web hosting account via SSH<\/a>.<\/p>\n\n\n\nGo to the directory that you’ve chosen as application root for the app when you created it (according to the instructions above<\/a>).<\/p>\n\n\n\nThen create the folder tmp<\/code> in your application root if it doesn’t already exist. Then create or modify the file restart.txt<\/code> in that folder to force your application to restart. For example, you may use the following command after cd<\/code>‘ing to the correct folder:<\/p>\n\n\n\ntouch tmp\/restart.txt<\/pre>\n\n\n\nSelect Node.js version<\/h3>\n\n\n\n
If you require Node.js to run certain cli scripts\/programs, and want to select what version of Node to run, you can use nvm<\/code> (Node Version Manager).<\/p>\n\n\n\nTo get started, you need to log on to your web hosting account via SSH<\/a>.<\/p>\n\n\n\n