* Update README.md in docker/alpine
- Replace contents with the usage of the image auto-built by Docker Cloud
- Add descriptions on the customizable environment variables
* Update Dockerfile maintainer list
Refer to #1914
* Install rng-tools as runtime dependency
* Remove unnecessary 'git submodule update', as Docker Cloud runs 'git submodule update' after cloning the repository
* Replace variable SERVER_PORT with fixed port 8388, as it can't be customized with -e anyway
* Use the repository as context, instead of released .tar.gz
* Remove version information from Dockerfile, and let Docker Cloud handle it
* Add .dockerignore
Next steps:
1. Connect repository in Docker Cloud
2. Setup automated builds:
- A push on `master` branch triggers build for `unstable` tag
- A tag matching /^v[0-9]+(\.[0-9]+){2}$/ triggers build for a same-named tag
Refer to #1914
Alpine 3.7 libtool pkg depends on bash pkg, this caused the compile hangs at "checking that generated files are newer than configure...", after check [this thread](https://forums.docker.com/t/problem-of-hanging-autoreconf/41015/3), I remove libtool and it works.
fix these errors:
- ca-certificates missed
fatal: unable to access
'https://github.com/shadowsocks/shadowsocks-libev.git/': Problem with
the SSL CA cert (path? access rights?)
- automake missed
Can't exec "aclocal": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 326.
autoreconf: failed to run aclocal: No such file or directory
- libmbedtls-dev
checking for mbedtls_cipher_setup in -lmbedcrypto... no
configure: error: mbed TLS libraries not found.
Add experimental HTTP/TLS obfuscating as an **optional extension** of shadowsocks protocol.
More discussions can be found here: https://github.com/shadowsocks/shadowsocks-org/issues/26
As this feature is still a SIP (Shadowsocks Improvement Proposal), it's very unstable and experimental. So,
1. Don't enable it unless you know what it is.
2. Be very careful when using it in production environment.