USocketNet – Run a Server Instance with CLI

You are here:
< Back
INITIALIZING NEW INSTANCE OF THE SERVER FOR CLI USER
PORT=3000 pm2 start --name Server-A server.js -- --name USocketNet-A

+ ‘PORT=3000′ (Optional): If this parameter is not passed during command execution or simply saying removing the ‘PORT=3000‘ from the command, the port variable which is declared on admin.json will be used to run a new instance of USocketNet server. On the other hand, if you declare a port by passing this argument, that port argument will be used.

+ ‘pm2 start’ (Required): Call or use the global dependency of PM2 npm package. You can install this just by running the run_npm-install.bat or execute a command in a Node JS environment, ‘npm install’ to get all the list of npm dependencies used by USocketNet. them automatically install or update.
+ ‘–name Server-A’ (Required): By declaring this argument, your new UsocketNet instance will be named to ‘Server-A‘. So, if you have multiple instances of the server and then you want to make the list of your server be reasonably named.
+ ‘server.js (Required): This is the main script of the USocketNet server to be called when we want to deploy a new instance of USocketNet server. This should not be changed as it will called the pre-exsiting server.js script on the root folder of the USocketNet.
+ ‘‘  (Optional): Separate pm2 arguments and node js arguments that we can also declare. This will be reserved for new features for our CLI users, which they can override variables from admin.json if they declared the specific and corresponding argument here.
+ ‘–name USocketNet-A‘ (Optional): ‘Name’ of the Node Js application or server instance. As of now, this is the first custom arguments of USocketNet which is to simply name the current NodeJS application.
Constantly evolving with the latest software design techniques and related technologies. Please feel free to browse my Qualifications.

Leave your Thoughts