Skip to content
GitLab
    • Explore Projects Groups Snippets
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W Wiki Home
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • VM4SEC Wiki
  • Wiki Home
  • Wiki
  • VM4SEC Dashboard

VM4SEC Dashboard · Changes

Page history
Update VM4SEC Dashboard authored 3 years ago by Dimitris Tsoukalas's avatar Dimitris Tsoukalas
Hide whitespace changes
Inline Side-by-side
Showing
with 2 additions and 2 deletions
+2 -2
VM4SEC-Dashboard.md
View page @ 2973a656
...@@ -29,7 +29,7 @@ npm install ...@@ -29,7 +29,7 @@ npm install
``` ```
- **Step 3**: Next, you must create an empty `.env` file in the root directory of the application. Then, copy the contents of the `.env-default` file (also found in root directory) inside the `.env` file. - **Step 3**: Next, you must create an empty `.env` file in the root directory of the application. Then, copy the contents of the `.env-default` file (also found in root directory) inside the `.env` file.
> **Important Notice:** The `.env` file contains all environment variables that hold host configurations for each required backend service (i.e., the endpoints of the *Project Management*, the *Quantitative Security Assessment* and the *Vulnerability Prediction* services). In case you have installed these services locally on your premises, you will need to modify these environment variables accordingly. Remember to restart the application each time you modify this file. > **Important Notice:** The `.env` file contains all environment variables that hold host configurations for each required backend service (i.e., the endpoints of the *Project Management*, the *Quantitative Security Assessment* and the *Vulnerability Prediction* services). In case you have installed these services locally on your premises, you will need to modify these environment variables accordingly, by providing the correct IP and PORT. Remember to restart the application each time you modify this file.
- **Step 4**: Finally, you can start the VM4SEC Dashboard server and a web page should open on your favorite browser. Open cmd and run the following command: - **Step 4**: Finally, you can start the VM4SEC Dashboard server and a web page should open on your favorite browser. Open cmd and run the following command:
```bash ```bash
npm start npm start
...@@ -44,7 +44,7 @@ Alternatively, you can install the VM4SEC Dashboard using Docker. ...@@ -44,7 +44,7 @@ Alternatively, you can install the VM4SEC Dashboard using Docker.
``` ```
cp ./.env-default ./.env cp ./.env-default ./.env
``` ```
> **Important Notice:** The `.env` file contains all environment variables that hold host configurations for each required backend service (i.e., the endpoints of the *Project Management*, the *Quantitative Security Assessment* and the *Vulnerability Prediction* services). In case you have installed these services locally on your premises, you will need to modify these environment variables accordingly. Remember to restart the application each time you modify this file. > **Important Notice:** The `.env` file contains all environment variables that hold host configurations for each required backend service (i.e., the endpoints of the *Project Management*, the *Quantitative Security Assessment* and the *Vulnerability Prediction* services). In case you have installed these services locally on your premises, you will need to modify these environment variables accordingly, by providing the correct IP and PORT. Remember to restart the application each time you modify this file.
- **Step 4**: Open cmd and run: - **Step 4**: Open cmd and run:
``` ```
sudo docker run -it \ sudo docker run -it \
......
Clone repository
  • Project Management API
  • Quantitative Security Assessment (QSA)
  • VM4SEC Dashboard
  • Vulnerability Prediction (VP)
  • Walkthrough
  • Home

Menu

Explore Projects Groups Snippets