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-02-17 03:34:54 +00:00
parent 67e2442c99
commit 288c724dda
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -1,7 +1,7 @@
[![Build Status](https://ci.quacker.org/api/badges/d/d2ray/status.svg)](https://ci.quacker.org/d/d2ray) [![Build Status](https://ci.quacker.org/api/badges/d/d2ray/status.svg)](https://ci.quacker.org/d/d2ray)
# Xray + VLESS + XTLS + Nginx fallback in Docker! # Xray + VLESS + XTLS + Nginx fallback in Docker!
## What is d2ray? ## What is d2ray?
d2ray is a single Docker container that provides easy and braindead configuration for Xray + XTLS + Nginx fallback. d2ray also offers currently hardcoded setup instructions and Xray binary packages for various OSes and architectures. d2ray is a single Docker container that provides easy and braindead configuration for xtls-vision + Nginx fallback. d2ray also offers currently hardcoded setup instructions and Xray binary packages for various OSes and architectures.
## Features ## Features
- Easy 5-minutes setup. - Easy 5-minutes setup.
@ -15,7 +15,7 @@ d2ray is a single Docker container that provides easy and braindead configuratio
- See `.env` in the current repo. - See `.env` in the current repo.
- `PORT`: the port to run Xray on. - `PORT`: the port to run Xray on.
- `FQDN`: the domain name of your server, used to generate SSL certificates. - `FQDN`: the domain name of your server, used to generate SSL certificates.
- `USERS`: comma separated list of `USERCONF` allowed access to both Xray and resource downloads. Each `USERCONF` is of format `userid@flow`. `userid` is used as the credential for Xray. If `flow` is not specified it defaults to `xtls-rprx-vision`. For example, setting `USERS` to `user1@xtls-rprx-direct,user2` means two users: `user1` with flow `xtls-rprx-direct` and `user2` with flow `xtls-rprx-vision`. - `USERS`: comma separated list of `USERCONF` allowed access to both Xray and resource downloads. Each `USERCONF` is of format `userid@flow`. `userid` is used as the credential for Xray. If `flow` is not specified it defaults to `xtls-rprx-vision`. For example, setting `USERS` to `user1@xtls-rprx-direct,user2` means two users: `user1` with flow `xtls-rprx-direct` and `user2` with flow `xtls-rprx-vision`. Note that since Xray 1.7.2, xtls-direct is deprecated so I recommend you not specify `flow` and just use the default.
- `LOGDIR`: the directory to store logs, currently required. - `LOGDIR`: the directory to store logs, currently required.
3. `docker compose up -d` 3. `docker compose up -d`
4. You can access the Xray service using an Xray client. You can access the per-user resource downloads by accessing `https://your-domain:your-port`, entering the `userid` in the textbox at the bottom of the page and clicking the `Download` button next to it. 4. You can access the Xray service using an Xray client. You can access the per-user resource downloads by accessing `https://your-domain:your-port`, entering the `userid` in the textbox at the bottom of the page and clicking the `Download` button next to it.