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
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ A clear and concise description of what you expected to happen.
36
36
- DefectDojo version (see footer) or commit message: [use `git show -s --format="[%ci] %h: %s [%d]"`]
37
37
38
38
**Logs**
39
-
Use `docker-compose logs` (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).
39
+
Use `dockercompose logs` (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).
40
40
41
41
**Sample scan files**
42
42
If applicable, add sample scan files to help reproduce your problem.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/support_request.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ A clear and concise description of what you expected to happen.
36
36
- DefectDojo version (see footer) or commit message: [use `git show -s --format="[%ci] %h: %s [%d]"`]
37
37
38
38
**Logs**
39
-
Use `docker-compose logs` (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).
39
+
Use `dockercompose logs` (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).
40
40
41
41
**Sample scan files**
42
42
If applicable, add sample scan files to help reproduce your problem.
Copy file name to clipboardExpand all lines: docs/content/en/contributing/how-to-write-a-parser.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ All commands assume that you're located at the root of the django-DefectDojo clo
15
15
- Checkout `dev` and make sure you're up to date with the latest changes.
16
16
- It's advised that you create a dedicated branch for your development, such as `git checkout -b parser-name`.
17
17
18
-
It is easiest to use the docker-compose deployment as it has hot-reload capbility for uWSGI.
18
+
It is easiest to use the dockercompose deployment as it has hot-reload capbility for uWSGI.
19
19
Set up your environment to use the debug environment:
20
20
21
21
`$ docker/setEnv.sh debug`
@@ -27,7 +27,7 @@ Please have a look at [DOCKER.md](https://github.com/DefectDojo/django-DefectDoj
27
27
You will want to build your docker images locally, and eventually pass in your local user's `uid` to be able to write to the image (handy for database migration files). Assuming your user's `uid` is `1000`, then:
28
28
29
29
{{< highlight bash >}}
30
-
$ docker-compose build --build-arg uid=1000
30
+
$ dockercompose build --build-arg uid=1000
31
31
{{< /highlight >}}
32
32
33
33
## Which files do you need to modify?
@@ -279,7 +279,7 @@ This ensures the file is closed at the end of the with statement, even if an exc
279
279
280
280
### Test database
281
281
282
-
To test your unit tests locally, you first need to grant some rights. Get your MySQL root password from the docker-compose logs, login as root and issue the following commands:
282
+
To test your unit tests locally, you first need to grant some rights. Get your MySQL root password from the dockercompose logs, login as root and issue the following commands:
283
283
284
284
{{< highlight mysql >}}
285
285
MYSQL> grant all privileges on test_defectdojo.* to defectdojo@'%';
@@ -291,17 +291,17 @@ MYSQL> flush privileges;
291
291
This local command will launch the unit test for your new parser
0 commit comments