d/d2ray
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update README.md
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
quackerd 2023-08-21 14:08:22 +00:00
parent ab07f40f58
commit 7cf924dccb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -22,7 +22,7 @@ d2ray checks whether a key file exists at path `/etc/xray/certs/keys` and genera
You can either supply a pre-generated private key using `xray x25519` or let d2ray generate one. The corresponding public key is printed to the container log (`docker logs`), which clients use to connect. You can either supply a pre-generated private key using `xray x25519` or let d2ray generate one. The corresponding public key is printed to the container log (`docker logs`), which clients use to connect.
If you are generating the private key yourself, the key file must contain exactly the output of `xray x25519`. If you are generating the keys yourself, the key file must contain exactly the output of `xray x25519`.
## How To Update? ## How To Update?
- `docker compose down` - `docker compose down`