Skip to content
GitLab
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 Mar 04, 2022 by Dimitris Tsoukalas's avatar Dimitris Tsoukalas
Hide whitespace changes
Inline Side-by-side
VM4SEC-Dashboard.md
View page @ c10fb2ad
......@@ -6,7 +6,7 @@ Charts and plots will be visualized with [highcharts](https://www.highcharts.com
Documentation for these frameworks can be found directly on their site.
All of these libraries are provided under MIT License and thus free to use in the VM4SEC project.
All of these libraries are provided under MIT License and thus are free to use in the VM4SEC project.
# Repository organization
Directories and files:
......@@ -19,6 +19,7 @@ Directories and files:
- `assets` contains artefacts like icons and images that are used within the components.
- `apis` contains the API calls to the backend services.
- `public` contains the files that are actually visible to everyone with access on the server.
- `.env-default` contains all environment variables that hold host configurations (e.g., URLS) for each backend service.
# Installation of VM4SEC Dashboard
- **Step 1**: Clone the latest VM4SEC Dashboard version that can be found in the present Gitlab repository and navigate to the root directory.
......@@ -26,7 +27,9 @@ Directories and files:
```bash
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. The `.env` file contains all environment variables that hold host configurations for each backend server, so you should modify environment variables accordingly. Remember to restart the application each time you modify this 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 backend service (e.g., URLS), so you should modify these environment variables accordingly. 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:
```bash
npm start
......@@ -41,6 +44,7 @@ Alternatively, you can install the VM4SEC Dashboard using Docker.
```
cp ./.env-default ./.env
```
**Important Notice:** The `.env` file contains all environment variables that hold host configurations for each backend service (e.g., URLS), so you should modify these environment variables accordingly. Remember to restart the application each time you modify this file.
- **Step 4**: Open cmd and run:
```
sudo docker run -it \
......
Clone repository
  • Project Management API
  • Quantitative Security Assessment (QSA)
  • VM4SEC Dashboard
  • Vulnerability Prediction (VP)
  • Walkthrough
  • Home