Skip to content

Commit b565c3c

Browse files
committed
Clarify docker instructions
1 parent 7b03d3d commit b565c3c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Readme.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -82,10 +82,10 @@ You can use the CLI tool within docker, for example to host a dockerised DarkRif
8282

8383
A simple example of this would be:
8484
```bash
85-
docker run --name darkrift -d -p 4296/tcp -p 4296/udp -v $PWD/project:/project -e DR_INVOICE_NO="if-using-pro" darkriftnetworking/darkrift-cli:latest
85+
docker run --name darkrift -d -p 4296:4296/tcp -p 4296:4296/udp -v $PWD/project:/project -e DR_INVOICE_NO="if-using-pro" darkriftnetworking/darkrift-cli:latest
8686
```
8787

88-
The `project` volume should contain a DarkRift project. Ports are provided as an example and will depend on the listener in use. By default, the command executed is `run`. The HTTP healthcheck plugin will need to be enabled and running on the default port of 10666.
88+
The `project` volume should contain a DarkRift project with a platform of `netcoreapp3.1` (and hence Pro is required). Ports are provided as an example and will depend on the listener in use. By default, the command executed is `run`. The HTTP healthcheck plugin will need to be enabled and running on the default port of 10666.
8989

9090
It is advised to set the DarkRift's data directory to a path outside of the project such as `/data`. It may be useful to assign this to a named volume if your plugins require persistence.
9191

0 commit comments

Comments
 (0)