This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Replace shadowsocks-libev&v2ray to shadowsocks-rust&xray-plugin #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Why shadowsocks-rust
According to shadowsocks-libev about future development moved to shadowsocks-rust.
Why xray-plugin
V2ray not updated a long time. Xray-plugin protocol backward compatible with v2ray, v2ray clients can connect to xray.
Why alpine
Much smaller base image. Now builded image has only 48 mb size. It can be reduced more with removing unused shadowsocks-rust apps(like sslocal).
Links to android app in README.md
Current links incorrect, replaced with links to last release page(not direct to apk).
Why leave v2ray for clients
In Play Market it's only v2ray plugin, no xray.
Need be checked
Is full domain name still can be specified
I use sh, not bash and something in entrypoint.sh can go wrong.
Is moving PASSWORD escaping direct to shadowsocks-libev_config.json is necessary
ssserver did not accept config a long time and I thought problem was in password string. Really problem was in qoutes around server_port. I don't remove changes with PASSWORD escaping.
Heroku blocked my account after I tested this changes so I can't check all in "Need be checked" by myshelf.