Software pre-requisites for the machine, on which you want to install vREST enterprise server:
Hardware requirements for the machine, on which you want to install vREST enterprise server:
- For vREST Enterprise Server:
- RAM: Minimum 2 GB (recommended 4 GB)
- CPU: A recent server (64 bit architecture). As of now, only single core will be utilised in multi core CPUs for enterprise server operations. In future, we intend to add support for utilising multiple cores of the CPU.
- Storage: Minimum 20GB HDD (7200 RPM or faster).
- Storage is basically needed for storing log files, config files and enterprise server binary.
- For data storage, a separate machine is recommended for MongoDB.
- For Mongo DB Server:
A separate machine is recommended for database server (MongoDB). For MongoDB server hardware considerations, please read this guide for better information based on your environment. However the recommended configuration for vREST is as follows:
- RAM: MInimum 2 GB (An increased capacity will result in increased performance.)
- CPU: A multi core server with 64 bit architecture will result in better performance.
- Storage: Minimum 40 GB (Sufficient to store around 1 lac test cases and their execution results)
Make a new directory of your choice and move the downloaded binary file (vrest_os_x_x_x) to this directory
$ mkdir vrest
$ cd vrest
vrest $ mv ~/Downloads/vrest_os_x_x_x .
- Set vREST Enterprise server configuration
In this new directory, create a new file `config.json`. A sample file content is attached below:
"port" : "4000",
"redirectToHTTPS" : false,
"disableAllEmails" : false,
"cookieSecret" : "your_db_secret",
"startOnHTTPS" : false,
"httpsPrivateKeyPath" : "privatekey.pem",
"httpsCertificatePath" : "certificate.pem",
"db" : "mongodb://localhost/vrest",
"disableAnalyticsTracking" : false,
"disableLiveChat" : false,
"defaultFrom": "vREST Mail <firstname.lastname@example.org>",
- The above file contains the following configuration:
Port Number on which, you want to execute vREST Enterprise server.
Boolean flag. If set to true, then any incoming requests with scheme HTTP will be redirected to HTTPS.
Boolean flag. If set to true, then vREST Enterprise server will stop sending any emails.
Cookie secret. Set this to any secret string.
Boolean flag. If set to true then vREST Enterprise server will try to start on HTTPS. If you set true, then please set appropriate configuration for port, httpsPrivateKeyPath, httpsCertificatePath.
If startOnHTTPS config is set to true then provide the file name of the private key. This private key must reside in the same directory where config.json file is written.
If startOnHTTPS config is set to true then provide the file name of certificate file. This certificate file also must reside in the same directory where config.json file is written.
MongoDB connection string. For more information, please read this guide link.
By default, google analytics is enabled. We recommend you to keep this option enabled. If you want to disable google analytics, then you may set it to true.
By default, live chat option is enabled. If you want to disable live chat, then you may set it to true.
[Added in v220.127.116.11] If provided null or option not provided then random password is set for new users. Otherwise you may set the default password for new users by using this property. Default password must be of type string and must be minimum 8 characters long.
Provide mail configuration here. Key `options` introduced in vREST 2.9.9 and here you may define other mail options such authMethod. For full options list, please visit NodeMailer Document.
Start the server
To start the server, first make sure that your MongoDB server is running and you have configured the config.json file. Now simply run the following command:
vrest$ chmod +x vrest_os_x_x_x
That's it. Your vREST Enterprise server is ready and accessible from URL like this: http(s)://<computer_name_or_IP_address>:<port>. Please follow this guide link to install licence in your enterprise instance.
Note: Please make sure, you are accessing vREST Enterprise through public facing URL before generating the licence key.