You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In proxy enviroments the .env configuration must be added directly to the Dockerfiles.
34
-
35
32
#### Get API Keys
36
33
37
34
- How to get a *GitHub*[API key](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).
@@ -54,3 +51,30 @@ Enter [here](http://0.0.0.0:3000) for the frontend Web API.
54
51
1. It is recommended to use a GUI such as [MongoDB Compass](https://www.mongodb.com/en/products/compass) to see what information is being indexed in vulnerability database.
55
52
56
53
2. You can see the created graph built for [pip](http://0.0.0.0:7474/browser/), [npm](http://localhost:7473/browser/) and [mvn](http://localhost:7472/browser/) clicking in this names. Using the Neo4J browser interfaces.
54
+
55
+
## Proxy Enviroment
56
+
57
+
### Create an *.env* file por proxy settings
58
+
59
+
Define these variables in an *.env* file that can be referenced by *docker-compose.yml*. Example *.env* file:
60
+
61
+
```
62
+
HTTP_PROXY=http://proxy.example.com:port
63
+
HTTPS_PROXY=https://proxy.example.com:port
64
+
NO_PROXY=localhost,127.0.0.1
65
+
```
66
+
67
+
### Add an *.env* to the *docker-compose.yml*
68
+
69
+
Add the proxy configuration defined in the *.env* file, for example to the following *docker-compose.yml* file:
0 commit comments