Update README.md
This commit is contained in:
parent
2340e8e7e2
commit
6ca886ab98
11
README.md
11
README.md
|
|
@ -1 +1,10 @@
|
|||
# dockerfiles
|
||||
# dockerfiles
|
||||
不定期收集,整理和编写常用优秀软件和服务的 Dockerfile 文件.
|
||||
大部分已构建 X86 和 ARM 架构 docker 镜像,详情查看 [Docker Hub](https://hub.docker.com/u/stilleshan) 直接使用.
|
||||
|
||||
|
||||
## Links
|
||||
GitHub https://github.com/stilleshan
|
||||
Docker https://hub.docker.com/u/stilleshan
|
||||
Blog https://www.ioiox.com
|
||||
|
||||
|
|
|
|||
|
|
@ -1,258 +1,13 @@
|
|||
# AnyLink
|
||||
|
||||
[](https://github.com/bjdgyc/anylink/actions)
|
||||
[](https://pkg.go.dev/github.com/bjdgyc/anylink)
|
||||
[](https://goreportcard.com/report/github.com/bjdgyc/anylink)
|
||||
[](https://codecov.io/gh/bjdgyc/anylink)
|
||||
|
||||
|
||||
|
||||
|
||||
AnyLink 是一个企业级远程办公sslvpn的软件，可以支持多人同时在线使用。
|
||||
|
||||
## Repo
|
||||
|
||||
> github: https://github.com/bjdgyc/anylink
|
||||
|
||||
> gitee: https://gitee.com/bjdgyc/anylink
|
||||
|
||||
## Introduction
|
||||
|
||||
AnyLink 基于 [ietf-openconnect](https://tools.ietf.org/html/draft-mavrogiannopoulos-openconnect-02)
|
||||
协议开发，并且借鉴了 [ocserv](http://ocserv.gitlab.io/www/index.html) 的开发思路，使其可以同时兼容 AnyConnect 客户端。
|
||||
|
||||
AnyLink 使用TLS/DTLS进行数据加密，因此需要RSA或ECC证书，可以通过 Let's Encrypt 和 TrustAsia 申请免费的SSL证书。
|
||||
|
||||
AnyLink 服务端仅在CentOS 7、Ubuntu 18.04测试通过，如需要安装在其他系统，需要服务端支持tun/tap功能、ip设置命令。
|
||||
|
||||
## Screenshot
|
||||
|
||||
|
||||
|
||||
## Installation
|
||||
|
||||
> 没有编程基础的同学建议直接下载release包，从下面的地址下载 anylink-deploy.tar.gz
|
||||
>
|
||||
> https://github.com/bjdgyc/anylink/releases
|
||||
|
||||
> 升级 go version = 1.15
|
||||
>
|
||||
> 需要提前安装好 golang 和 nodejs
|
||||
|
||||
```shell
|
||||
git clone https://github.com/bjdgyc/anylink.git
|
||||
|
||||
cd anylink
|
||||
sh build.sh
|
||||
|
||||
# 注意使用root权限运行
|
||||
cd anylink-deploy
|
||||
sudo ./anylink --conf="conf/server.toml"
|
||||
|
||||
# 默认管理后台访问地址
|
||||
# http://host:8800
|
||||
# 默认账号密码
|
||||
# admin 123456
|
||||
|
||||
```
|
||||
|
||||
## Feature
|
||||
|
||||
- [x] IP分配(实现IP、MAC映射信息的持久化)
|
||||
- [x] TLS-TCP通道
|
||||
- [x] DTLS-UDP通道
|
||||
- [x] 兼容AnyConnect
|
||||
- [x] 基于tun设备的nat访问模式
|
||||
- [x] 基于tap设备的桥接访问模式
|
||||
- [x] 支持 [proxy protocol v1](http://www.haproxy.org/download/2.2/doc/proxy-protocol.txt) 协议
|
||||
- [x] 用户组支持
|
||||
- [x] 多用户支持
|
||||
- [x] TOTP令牌支持
|
||||
- [x] TOTP令牌开关
|
||||
- [x] 流量控制
|
||||
- [x] 后台管理界面
|
||||
- [x] 访问权限管理
|
||||
|
||||
## Config
|
||||
|
||||
默认配置文件内有详细的注释，根据注释填写配置即可。
|
||||
|
||||
```shell
|
||||
# 生成后台密码
|
||||
./anylink tool -p 123456
|
||||
|
||||
# 生成jwt密钥
|
||||
./anylink tool -s
|
||||
```
|
||||
|
||||
[conf/server.toml](server/conf/server.toml)
|
||||
|
||||
## Setting
|
||||
|
||||
> 以下参数必须设置其中之一
|
||||
|
||||
网络模式选择，需要配置 `link_mode` 参数，如 `link_mode="tun"`,`link_mode="tap"` 两种参数。 不同的参数需要对服务器做相应的设置。
|
||||
|
||||
建议优先选择tun模式，因客户端传输的是IP层数据，无须进行数据转换。 tap模式是在用户态做的链路层到IP层的数据互相转换，性能会有所下降。 如果需要在虚拟机内开启tap模式，请确认虚拟机的网卡开启混杂模式。
|
||||
|
||||
### tun设置
|
||||
|
||||
1. 开启服务器转发
|
||||
|
||||
```shell
|
||||
# flie: /etc/sysctl.conf
|
||||
net.ipv4.ip_forward = 1
|
||||
|
||||
#执行如下命令
|
||||
sysctl -w net.ipv4.ip_forward=1
|
||||
```
|
||||
|
||||
2. 设置nat转发规则
|
||||
|
||||
```shell
|
||||
# 请根据服务器内网网卡替换 eth0
|
||||
iptables -t nat -A POSTROUTING -s 192.168.10.0/24 -o eth0 -j MASQUERADE
|
||||
# 如果执行第一个命令不生效，可以继续执行下面的命令
|
||||
# iptables -A FORWARD -i eth0 -s 192.168.10.0/24 -j ACCEPT
|
||||
# 查看设置是否生效
|
||||
iptables -nL -t nat
|
||||
```
|
||||
|
||||
3. 使用AnyConnect客户端连接即可
|
||||
|
||||
### tap设置
|
||||
|
||||
1. 创建桥接网卡
|
||||
|
||||
```
|
||||
注意 server.toml 的ip参数，需要与 bridge-init.sh 的配置参数一致
|
||||
```
|
||||
|
||||
2. 修改 bridge-init.sh 内的参数
|
||||
|
||||
```
|
||||
eth="eth0"
|
||||
eth_ip="192.168.1.4"
|
||||
eth_netmask="255.255.255.0"
|
||||
eth_broadcast="192.168.1.255"
|
||||
eth_gateway="192.168.1.1"
|
||||
```
|
||||
|
||||
3. 执行 bridge-init.sh 文件
|
||||
|
||||
```
|
||||
sh bridge-init.sh
|
||||
```
|
||||
|
||||
## Systemd
|
||||
|
||||
添加 systemd脚本
|
||||
|
||||
* anylink 程序目录放入 `/usr/local/anylink-deploy`
|
||||
|
||||
systemd 脚本放入：
|
||||
|
||||
* centos: `/usr/lib/systemd/system/`
|
||||
* ubuntu: `/lib/systemd/system/`
|
||||
|
||||
操作命令:
|
||||
|
||||
* 启动: `systemctl start anylink`
|
||||
* 停止: `systemctl stop anylink`
|
||||
* 开机自启: `systemctl enable anylink`
|
||||
|
||||
## Docker
|
||||
|
||||
1. 获取镜像
|
||||
|
||||
```bash
|
||||
docker pull bjdgyc/anylink:latest
|
||||
```
|
||||
|
||||
2. 生成密码
|
||||
|
||||
```bash
|
||||
docker run -it --rm bjdgyc/anylink tool -p 123456
|
||||
#Passwd:$2a$10$lCWTCcGmQdE/4Kb1wabbLelu4vY/cUwBwN64xIzvXcihFgRzUvH2a
|
||||
```
|
||||
|
||||
3. 生成jwt secret
|
||||
|
||||
```bash
|
||||
docker run -it --rm bjdgyc/anylink tool -s
|
||||
#Secret:9qXoIhY01jqhWIeIluGliOS4O_rhcXGGGu422uRZ1JjZxIZmh17WwzW36woEbA
|
||||
```
|
||||
|
||||
4. 启动容器
|
||||
|
||||
```bash
|
||||
docker run -itd --name anylink --privileged \
|
||||
-p 443:443 -p 8800:8800 \
|
||||
--restart=always \
|
||||
bjdgyc/anylink
|
||||
```
|
||||
|
||||
5. 使用自定义参数启动容器
|
||||
|
||||
```bash
|
||||
docker run -itd --name anylink --privileged \
|
||||
-e IPV4_CIDR=192.168.10.0/24 \
|
||||
-p 443:443 -p 8800:8800 \
|
||||
--restart=always \
|
||||
bjdgyc/anylink \
|
||||
-c=/etc/server.toml --admin_addr=:8080
|
||||
```
|
||||
|
||||
6. 构建镜像
|
||||
|
||||
```bash
|
||||
#获取仓库源码
|
||||
git clone https://github.com/bjdgyc/anylink.git
|
||||
# 构建镜像
|
||||
docker build -t anylink .
|
||||
```
|
||||
|
||||
## 常见问题
|
||||
|
||||
请前往 [问题地址](question.md) 查看具体信息
|
||||
|
||||
## Discussion
|
||||
|
||||
|
||||
|
||||
添加QQ群: 567510628
|
||||
|
||||
QQ群共享文件有相关软件下载
|
||||
|
||||
## Contribution
|
||||
|
||||
欢迎提交 PR、Issues，感谢为AnyLink做出贡献。
|
||||
|
||||
注意新建PR，需要提交到dev分支，其他分支暂不会合并。
|
||||
|
||||
## Other Screenshot
|
||||
|
||||
<details>
|
||||
<summary>展开查看</summary>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
</details>
|
||||
|
||||
## License
|
||||
|
||||
本项目采用 MIT 开源授权许可证，完整的授权说明已放置在 LICENSE 文件中。
|
||||
|
||||
## Thank
|
||||
|
||||
<a href="https://www.jetbrains.com">
|
||||
<img src="screenshot/jetbrains.png" width="200" height="200" alt="jetbrains.png" />
|
||||
</a>
|
||||
# anylink
|
||||
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/anylink](https://hub.docker.com/r/stilleshan/anylink)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
## 使用
|
||||
本仓库参考 [bjdgyc/anylink](https://github.com/bjdgyc/anylink) 构建 X86 和 ARM 平台 docker 镜像,具体使用教程请参考原作者仓库.
|
||||
|
||||
## 参考
|
||||
[开源企业级远程办公 VPN 软件 AnyLink 的 docker 部署及使用心得](https://www.ioiox.com/archives/128.html)
|
||||
[群晖NAS高级服务 - docker 部署 AnyLink 企业级远程办公 VPN 服务](https://www.ioiox.com/archives/129.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,158 +1,12 @@
|
|||
[cheveretourl]: https://chevereto.com/
|
||||
[cheveretogithub]: https://github.com/Chevereto/Chevereto-Free
|
||||
# chevereto
|
||||
|
||||
[][cheveretourl]
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/chevereto](https://hub.docker.com/r/stilleshan/chevereto)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
# nmtan/chevereto - Chevereto Free Docker
|
||||
## 使用
|
||||
本仓库参考 [tanmng/docker-chevereto](https://github.com/tanmng/docker-chevereto) 构建 X86 和 ARM 平台 docker 镜像,具体使用教程请参考原作者仓库.
|
||||
|
||||
[Chevereto][cheveretourl] is a powerful and fast image hosting script that allows you to create your very own full featured image hosting website in just minutes.
|
||||
## 参考
|
||||
[docker compose 部署迁移 Chevereto 图床程序教程](https://www.ioiox.com/archives/80.html)
|
||||
|
||||
Please note that the `installer` tag will provide you with the installer script
|
||||
from Chevereto, which can be used to install either the [free Chevereto version][cheveretogithub]
|
||||
or the paid version, while all the other tags will only provide the [free version][cheveretogithub].
|
||||
|
||||
## Supported tags and respective Dockerfile links
|
||||
|
||||
> Here we list only the most relevant and recent tags, for the full list, please
|
||||
use the `tags` tab in [Dockerhub page](https://hub.docker.com/r/nmtan/chevereto)
|
||||
|
||||
* `latest` - Using latest commit of the branch `master` from [original repo][cheveretogithub] ([Dockerfile](https://github.com/tanmng/docker-chevereto/blob/master/latest/Dockerfile))
|
||||
* `installer` - Using latest [installer script](https://cdn.rawgit.com/Chevereto/php-repo-installer/master/index.php) ([Dockerfile-installer](https://github.com/tanmng/docker-chevereto/blob/master/Dockerfile-installer)) - Once you start the container with this image, you will have to wait for it to download latest source code from [original repo][cheveretogithub]
|
||||
* `1.3.0` - Using the [`1.3.0` release](https://github.com/Chevereto/Chevereto-Free/releases/tag/1.3.0) ([Dockerfile](https://github.com/tanmng/docker-chevereto/blob/master/Dockerfile))
|
||||
* `1.2.3` - Using the [`1.2.3` release](https://github.com/Chevereto/Chevereto-Free/releases/tag/1.2.3) ([Dockerfile](https://github.com/tanmng/docker-chevereto/blob/master/Dockerfile))
|
||||
* `1.2.2` - Using the [`1.2.2` release](https://github.com/Chevereto/Chevereto-Free/releases/tag/1.2.2) ([Dockerfile](https://github.com/tanmng/docker-chevereto/blob/master/Dockerfile))
|
||||
* `1.2.1` - Using the [`1.2.1` release](https://github.com/Chevereto/Chevereto-Free/releases/tag/1.2.1) ([Dockerfile](https://github.com/tanmng/docker-chevereto/blob/master/Dockerfile))
|
||||
* `1.2.0` - Using the [`1.2.0` release](https://github.com/Chevereto/Chevereto-Free/releases/tag/1.2.0) ([Dockerfile](https://github.com/tanmng/docker-chevereto/blob/master/Dockerfile))
|
||||
* `1.1.4` - Using the [`1.1.4` release](https://github.com/Chevereto/Chevereto-Free/releases/tag/1.1.4) ([Dockerfile](https://github.com/tanmng/docker-chevereto/blob/master/Dockerfile))
|
||||
|
||||
> Note on PHP version: [Chevereto](cheveretourl) added support for PHP 7.4 since release `1.3.0`, PHP 7.3 since release `1.2.0`, PHP 7.2 since release `1.1.0`, and support for PHP 7.1 since release `1.0.6`, thus, the Docker images use the appropriate version of PHP to ensure the best performance and stability. You can check the [images' labels](https://docs.docker.com/config/labels-custom-metadata/) (by running `docker image inspect IMAGE_NAME`) for this information.
|
||||
|
||||
> Some older tag of Chevereto are no longer supported to save up on build resources
|
||||
|
||||
## Environment variables
|
||||
|
||||
The most essentials environments variables are listed below
|
||||
|
||||
* `CHEVERETO_DB_HOST` - Hostname of the Database machine that you wish to connect, default to `db`
|
||||
* `CHEVERETO_DB_PORT` - The port of the Database machine to connect to, default to `3306`
|
||||
* `CHEVERETO_DB_USERNAME` - Username to authenticate to MySQL database, default to `chevereto`
|
||||
* `CHEVERETO_DB_PASSWORD` - Password of the user when connect to MySQL database, default to `chevereto`
|
||||
* `CHEVERETO_DB_NAME` - Name of the database in MySQL server, default to `chevereto`
|
||||
* `CHEVERETO_DB_PREFIX` - Table prefix (you can use this to run multiple instance of Chevereto using the same Database), default to `chv_`
|
||||
|
||||
> For other environment variables, please consult the file [`settings.php`](https://github.com/tanmng/docker-chevereto/blob/master/settings.php) and the section "Advanced configuration" below.
|
||||
|
||||
## Connection to database
|
||||
|
||||
[Chevereto][cheveretourl] requires an Mysql database to store its information. You can use a [Mysql](https://hub.docker.com/_/mysql/) or [MariaDB](https://hub.docker.com/_/mariadb/) container to host this.
|
||||
|
||||
Information on connection to database is provided to container via environment variables explained above.
|
||||
|
||||
## Persistent storage
|
||||
|
||||
[Chevereto][cheveretourl] stores images uploaded by users in `/var/www/html/images` directory within the container.
|
||||
|
||||
You can mount a [data volume](https://docs.docker.com/engine/tutorials/dockervolumes/#data-volumes) at this location to ensure that you don't lose your images if you relaunch/remove container.
|
||||
|
||||
## Max image size
|
||||
|
||||
By default, PHP allow a maximum file upload to be 2MB. You can change such behaviour by updating the `php.ini` in your container, either by bind-mount the file, or build a new image with the updated file, that way you can reuse the image on demand.
|
||||
|
||||
> Note that by default, Chevereto set a file upload limit of 10MB, so after you modify your `php.ini`, you should also update this settings in Chevereto settings page (available at CHEVERETO_URL/dashboard/settings/image-upload)
|
||||
|
||||
> The customized `php.ini` should set the values of `upload_max_filesize`, `post_max_size` and potentially `memory_limit`, as showed in [the discussion from Chevereto Forum](https://chevereto.com/community/threads/chevereto-supports-only-2mb-max-upload-size.4729/). Further details on these parameters are available from [PHP documentation](http://php.net/manual/en/ini.core.php)
|
||||
|
||||
An example of this is available in the [`examples/bigger-files` directory](examples/bigger-files)
|
||||
|
||||
## Advanced configuration
|
||||
|
||||
Chevereto is written using the [`G\` framework](https://g.chevereto.com/) which supports some [advanced configurations](https://github.com/Chevereto/Chevereto-Free/blob/master/lib/G/G.php). Ultimate, that means we can use the variable `$settings` from `settings.php` to add more configurations to the applications. I have added multiple environment variables to support these configurations, please consult [the file `settings.php` from the repo](https://github.c m/tanmng/docker-chevereto/blob/master/settings.php) for the list of these environment variables as well as their purpose. Among these settings, I would say the following two are the most useful
|
||||
|
||||
* `CHEVERETO_SESSION_SAVE_PATH` - Specify where Chevereto can save the user session. Combining this with a shared volume/EFS/File synching, you can set up a highly available cluster of Free Chevereto while ensure user login status are not lost if they reconnect to another container.
|
||||
* `CHEVERETO_DEFAULT_TIMEZONE` - Specify the default timezone for any newly created/registered user, please make sure to use a [PHP supported value](https://www.php.net/manual/en/timezones.php) eg. `America/New_York`.
|
||||
|
||||
|
||||
## Example Usage
|
||||
|
||||
I recommend you to use [Docker-compose](https://docs.docker.com/compose/) / [Docker swarm](https://docs.docker.com/engine/swarm/) to launch Chevereto in conjunction with a MySQL database. A sample of docker-compose.yaml can be found below.
|
||||
|
||||
### Docker compose
|
||||
|
||||
```yaml
|
||||
version: '3'
|
||||
|
||||
services:
|
||||
db:
|
||||
image: mariadb
|
||||
volumes:
|
||||
- database:/var/lib/mysql:rw
|
||||
restart: always
|
||||
networks:
|
||||
- private
|
||||
environment:
|
||||
MYSQL_ROOT_PASSWORD: chevereto_root
|
||||
MYSQL_DATABASE: chevereto
|
||||
MYSQL_USER: chevereto
|
||||
MYSQL_PASSWORD: chevereto
|
||||
|
||||
chevereto:
|
||||
depends_on:
|
||||
- db
|
||||
image: nmtan/chevereto
|
||||
restart: always
|
||||
networks:
|
||||
- private
|
||||
environment:
|
||||
CHEVERETO_DB_HOST: db
|
||||
CHEVERETO_DB_USERNAME: chevereto
|
||||
CHEVERETO_DB_PASSWORD: chevereto
|
||||
CHEVERETO_DB_NAME: chevereto
|
||||
CHEVERETO_DB_PREFIX: chv_
|
||||
volumes:
|
||||
- chevereto_images:/var/www/html/images:rw
|
||||
ports:
|
||||
- 8080:80
|
||||
|
||||
networks:
|
||||
private:
|
||||
volumes:
|
||||
database:
|
||||
chevereto_images:
|
||||
```
|
||||
|
||||
Once `docker-compose.yaml` is ready, you can run
|
||||
|
||||
```bash
|
||||
docker-compose up
|
||||
```
|
||||
|
||||
To run the service
|
||||
|
||||
### Standalone
|
||||
|
||||
```bash
|
||||
docker run -it --name chevereto -d \
|
||||
--link mysql:mysql \
|
||||
-p 80:80 \
|
||||
-v "$PWD/images":/var/www/html/images \
|
||||
-e "CHEVERETO_DB_HOST=db" \
|
||||
-e "CHEVERETO_DB_USERNAME=chevereto" \
|
||||
-e "CHEVERETO_DB_PASSWORD=chevereto" \
|
||||
-e "CHEVERETO_DB_NAME=chevereto" \
|
||||
-e "CHEVERETO_DB_PREFIX=chv_" \
|
||||
nmtan/chevereto
|
||||
```
|
||||
|
||||
## Note on multi platform
|
||||
|
||||
It is feasible to run a Docker container image on different architectures. For now, I don't yet have the time to work on this, but will make sure to include that in future releases.
|
||||
|
||||
## Contributions
|
||||
|
||||
For now, this project is being maintained solely by me, for any questions or suggestions of improvements, please feel free [to reach out](mailto:tan.mng90@gmail.com)
|
||||
|
||||
## License
|
||||
|
||||
The docker image is released under the [MIT license](LICENSE)
|
||||
|
||||
Please note that [Chevereto](cheveretourl) is a product of [Rodolfo Berrios](http://rodolfoberrios.com/), this project aims mainly at encapsulating the free version (released under AGPL v3 License) into a Docker container image, which can then be used easily.
|
||||
|
|
|
|||
|
|
@ -1,56 +1,9 @@
|
|||
# ga-proxy
|
||||
|
||||
[](https://travis-ci.com/giuem/ga-proxy)
|
||||
[](https://hub.docker.com/r/giuem/ga-proxy/)
|
||||
[](https://github.com/giuem/ga-proxy/releases/latest)
|
||||
[](https://unpkg.com/@giuem/ga-proxy/dist/)
|
||||
[](https://www.jsdelivr.com/package/npm/@giuem/ga-proxy)
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/ga-proxy](https://hub.docker.com/r/stilleshan/ga-proxy)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
Accelerate Google Analytics.
|
||||
## 使用
|
||||
本仓库参考 [giuem/ga-proxy](https://github.com/giuem/ga-proxy) 构建 X86 和 ARM 平台 docker 镜像,具体使用教程请参考原作者仓库.
|
||||
|
||||
## Get Start
|
||||
|
||||
### Run via Docker
|
||||
|
||||
```bash
|
||||
docker pull giuem/ga-proxy
|
||||
docker run -d -p <port>:80 --name <container_name> giuem/ga-proxy
|
||||
```
|
||||
|
||||
### Run as you like
|
||||
|
||||
#### 1. Install
|
||||
|
||||
Download binary from [release](https://github.com/giuem/ga-proxy/releases) or build yourself.
|
||||
|
||||
#### 2. Run
|
||||
|
||||
```
|
||||
GIN_MODE=release ./ga-proxy [arguments]
|
||||
```
|
||||
|
||||
options:
|
||||
|
||||
```
|
||||
--ip IP, -i IP IP to listen (default: "127.0.0.1") [$IP]
|
||||
--port port, -p port port to listen (default: "9080") [$PORT]
|
||||
```
|
||||
|
||||
e.g.
|
||||
|
||||
```
|
||||
./ga_proxy -i 0.0.0.0 -p 80
|
||||
```
|
||||
|
||||
### 3. Insert script to your website
|
||||
|
||||
``` html
|
||||
<script>
|
||||
// replace following variables to your own
|
||||
window.ga_tid = "UA-XXXXX-Y";
|
||||
window.ga_url = "https://ga.giuem.com";
|
||||
</script>
|
||||
<script src="https://unpkg.com/@giuem/ga-proxy/dist/ga.min.js" async></script>
|
||||
```
|
||||
|
||||
Note: `ga.giuem.com` is my own service, it do not promise any SLA and may shutdown at some day. You'd better deploy your own server.
|
||||
|
|
|
|||
|
|
@ -1,110 +1,12 @@
|
|||
# gh-proxy
|
||||
|
||||
## 简介
|
||||
|
||||
github release、archive以及项目文件的加速项目，支持clone，有Cloudflare Workers无服务器版本以及Python版本
|
||||
|
||||
## 演示
|
||||
|
||||
[https://gh.api.99988866.xyz/](https://gh.api.99988866.xyz/)
|
||||
|
||||
演示站为公共服务，如有大规模使用需求请自行部署，演示站有点不堪重负
|
||||
|
||||
|
||||
|
||||
当然也欢迎[捐赠](#捐赠)以支持作者
|
||||
|
||||
## python版本和cf worker版本差异
|
||||
|
||||
- python版本支持进行文件大小限制，超过设定返回原地址 [issue #8](https://github.com/hunshcn/gh-proxy/issues/8)
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/gh-proxy](https://hub.docker.com/r/stilleshan/gh-proxy)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
## 使用
|
||||
|
||||
直接在copy出来的url前加`https://gh.api.99988866.xyz/`即可
|
||||
|
||||
也可以直接访问，在input输入
|
||||
|
||||
***大量使用请自行部署，以上域名仅为演示使用。***
|
||||
|
||||
以下都是合法输入（仅示例，文件不存在）：
|
||||
|
||||
- 分支源码：https://github.com/hunshcn/project/archive/master.zip
|
||||
|
||||
- release源码：https://github.com/hunshcn/project/archive/v0.1.0.tar.gz
|
||||
|
||||
- release文件：https://github.com/hunshcn/project/releases/download/v0.1.0/example.zip
|
||||
|
||||
- 分支文件：https://github.com/hunshcn/project/blob/master/filename
|
||||
|
||||
- commit文件：https://github.com/hunshcn/project/blob/1111111111111111111111111111/filename
|
||||
|
||||
- gist：https://gist.githubusercontent.com/cielpy/351557e6e465c12986419ac5a4dd2568/raw/cmd.py
|
||||
|
||||
## cf worker版本部署
|
||||
|
||||
首页：https://workers.cloudflare.com
|
||||
|
||||
注册，登陆，`Start building`，取一个子域名，`Create a Worker`。
|
||||
|
||||
复制 [index.js](https://cdn.jsdelivr.net/hunshcn/gh-proxy@master/index.js) 到左侧代码框，`Save and deploy`。如果正常，右侧应显示首页。
|
||||
|
||||
`index.js`默认配置下clone走github.com.cnpmjs.org，项目文件会走jsDeliver，如需走worker，修改Config变量即可
|
||||
|
||||
`ASSET_URL`是静态资源的url（实际上就是现在显示出来的那个输入框单页面）
|
||||
|
||||
`PREFIX`是前缀，默认（根路径情况为"/"），如果自定义路由为example.com/gh/*，请将PREFIX改为 '/gh/'，注意，少一个杠都会错！
|
||||
|
||||
## Python版本部署
|
||||
|
||||
### Docker部署
|
||||
|
||||
```
|
||||
docker run -d --name="gh-proxy-py" \
|
||||
-p 0.0.0.0:80:80 \
|
||||
--restart=always \
|
||||
hunsh/gh-proxy-py:latest
|
||||
```
|
||||
|
||||
第一个80是你要暴露出去的端口
|
||||
|
||||
### 直接部署
|
||||
|
||||
安装依赖（请使用python3）
|
||||
|
||||
```pip install flask requests```
|
||||
|
||||
按需求修改`app/main.py`的前几项配置
|
||||
|
||||
### 注意
|
||||
|
||||
python版本的机器如果无法正常访问github.io会启动报错，请自行修改静态文件url
|
||||
|
||||
workers版本默认配置下clone走github.com.cnpmjs.org，项目文件会走jsDeliver，如需走服务器，修改配置即可
|
||||
|
||||
python版本默认走服务器（2021.3.27更新）
|
||||
|
||||
## Cloudflare Workers计费
|
||||
|
||||
到 `overview` 页面可参看使用情况。免费版每天有 10 万次免费请求，并且有每分钟1000次请求的限制。
|
||||
|
||||
如果不够用，可升级到 $5 的高级版本，每月可用 1000 万次请求（超出部分 $0.5/百万次请求）。
|
||||
|
||||
## Changelog
|
||||
|
||||
* 2020.04.10 增加对`raw.githubusercontent.com`文件的支持
|
||||
* 2020.04.09 增加Python版本（使用Flask）
|
||||
* 2020.03.23 新增了clone的支持
|
||||
* 2020.03.22 初始版本
|
||||
|
||||
## 链接
|
||||
|
||||
[我的博客](https://hunsh.net)
|
||||
本仓库参考 [hunshcn/gh-proxy](https://github.com/hunshcn/gh-proxy) 构建 X86 和 ARM 平台 docker 镜像,具体使用教程请参考原作者仓库.
|
||||
|
||||
## 参考
|
||||
[ghproxy.com](https://ghproxy.com)
|
||||
|
||||
[jsproxy](https://github.com/EtherDream/jsproxy/)
|
||||
|
||||
## 捐赠
|
||||
|
||||
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
# goproxy for docker
|
||||
# goproxy
|
||||
|
||||
GitHub [stilleshan/dockerfile](https://github.com/stilleshan/dockerfile)
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/goproxy](https://hub.docker.com/r/stilleshan/goproxy)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
|
|
@ -24,8 +24,12 @@ docker run -d --name goproxy --restart always --network host stilleshan/goproxy
|
|||
> *更多服务参考 [snail007/goproxy](https://github.com/snail007/goproxy) 自行添加命令,每项服务命令之间使用 **&** 符号分隔,最后一项服务命令末尾无需 **&** 符号.*
|
||||
|
||||
## docker compose 启动
|
||||
下载 [docker-compose.yml](https://raw.githubusercontent.com/stilleshan/dockerfile/main/goproxy/docker-compose.yml) 执行以下命令启动:
|
||||
下载 [docker-compose.yml](https://raw.githubusercontent.com/stilleshan/dockerfiles/main/goproxy/docker-compose.yml) 执行以下命令启动:
|
||||
```shell
|
||||
docker-compose up -d
|
||||
```
|
||||
> *更多服务参考 [snail007/goproxy](https://github.com/snail007/goproxy) 自行添加命令,每项服务命令之间使用 **&** 符号分隔,最后一项服务命令末尾无需 **&** 符号.*
|
||||
|
||||
## 参考
|
||||
[轻量级高性能 HTTP/HTTPS SOCKS5 代理软件 goproxy docker 部署教程](https://www.ioiox.com/archives/131.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
## kms for docker
|
||||
## kms
|
||||
|
||||
GitHub [stilleshan/dockerfile](https://github.com/stilleshan/dockerfile)
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/kms](https://hub.docker.com/r/stilleshan/kms)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
|
|
@ -11,3 +11,4 @@ docker run -d --name kms --restart always -p 1688:1688 stilleshan/kms
|
|||
```
|
||||
|
||||
**注意:** 需开放防火墙`1688`端口
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
# ocserv for docker
|
||||
# ocserv
|
||||
|
||||
GitHub [stilleshan/dockerfile](https://github.com/stilleshan/dockerfile)
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/ocserv](https://hub.docker.com/r/stilleshan/ocserv)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
## 使用
|
||||
本仓库参考 [aminvakil/docker-ocserv](https://github.com/aminvakil/docker-ocserv) 构建 docker 镜像,主要用与自用和存档备份,具体使用教程请参考原作者仓库`README`文件.
|
||||
本仓库参考 [aminvakil/docker-ocserv](https://github.com/aminvakil/docker-ocserv) 构建 X86 和 ARM 平台 docker 镜像,具体使用教程请参考原作者仓库.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# tinyproxy for docker
|
||||
# tinyproxy
|
||||
|
||||
GitHub [stilleshan/dockerfile](https://github.com/stilleshan/dockerfile)
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/tinyproxy](https://hub.docker.com/r/stilleshan/tinyproxy)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
|
|
@ -10,7 +10,7 @@ docker run -d --name tinyproxy --restart always -p 8888:8888 stilleshan/tinyprox
|
|||
```
|
||||
|
||||
## docker compose 启动
|
||||
下载 [docker-compose.yml](https://raw.githubusercontent.com/stilleshan/dockerfile/main/tinyproxy/docker-compose.yml) 执行以下命令启动:
|
||||
下载 [docker-compose.yml](https://raw.githubusercontent.com/stilleshan/dockerfiles/main/tinyproxy/docker-compose.yml) 执行以下命令启动:
|
||||
```shell
|
||||
docker-compose up -d
|
||||
```
|
||||
|
|
@ -34,3 +34,7 @@ docker run -d --name tinyproxy --restart always -p 8888:8888 -v /path/tinyproxy.
|
|||
```shell
|
||||
curl -x https://user:password@IP:8888 https://ifconfig.co
|
||||
```
|
||||
|
||||
## 参考
|
||||
[轻量级 HTTP/HTTPS 代理软件 Tinyproxy docker 部署教程](https://www.ioiox.com/archives/130.html)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,395 +1,9 @@
|
|||
[](https://github.com/tiangolo/uwsgi-nginx-docker/actions?query=workflow%3ATest) [](https://github.com/tiangolo/uwsgi-nginx-docker/actions?query=workflow%3ADeploy)
|
||||
|
||||
## Supported tags and respective `Dockerfile` links
|
||||
|
||||
* [`python3.8`, `latest` _(Dockerfile)_](https://github.com/tiangolo/uwsgi-nginx-docker/blob/master/docker-images/python3.8.dockerfile)
|
||||
* [`python3.8-alpine` _(Dockerfile)_](https://github.com/tiangolo/uwsgi-nginx-docker/blob/master/docker-images/python3.8-alpine.dockerfile)
|
||||
* [`python3.7`, _(Dockerfile)_](https://github.com/tiangolo/uwsgi-nginx-docker/blob/master/docker-images/python3.7.dockerfile)
|
||||
* [`python3.6` _(Dockerfile)_](https://github.com/tiangolo/uwsgi-nginx-docker/blob/master/docker-images/python3.6.dockerfile)
|
||||
* [`python2.7` _(Dockerfile)_](https://github.com/tiangolo/uwsgi-nginx-docker/blob/master/docker-images/python2.7.dockerfile)
|
||||
|
||||
**Note**: Note: There are [tags for each build date](https://hub.docker.com/r/tiangolo/uwsgi-nginx/tags). If you need to "pin" the Docker image version you use, you can select one of those tags. E.g. `tiangolo/uwsgi-nginx:python3.7-2019-09-28`.
|
||||
|
||||
# uwsgi-nginx
|
||||
|
||||
**Docker** image with **uWSGI** and **Nginx** for web applications in **Python 3.6** and above, and **Python 2.7** (as **Flask**) in a single container. Optionally with Alpine Linux.
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/uwsgi-nginx](https://hub.docker.com/r/stilleshan/uwsgi-nginx)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
## Description
|
||||
## 使用
|
||||
本仓库参考 [tiangolo/uwsgi-nginx-docker](https://github.com/tiangolo/uwsgi-nginx-docker) 构建 X86 和 ARM 平台 docker 镜像,具体使用教程请参考原作者仓库.
|
||||
|
||||
This [**Docker**](https://www.docker.com/) image allows you to create [**Python**](https://www.python.org/) web applications that run with [**uWSGI**](https://uwsgi-docs.readthedocs.org/en/latest/) and [**Nginx**](http://nginx.org/en/) in a single container.
|
||||
|
||||
The combination of uWSGI with Nginx is a [common way to deploy Python web applications like Flask and Django](http://flask.pocoo.org/docs/1.0/deploying/uwsgi/). It is widely used in the industry and would give you decent performance. (*)
|
||||
|
||||
There is also an Alpine version. If you want it, check the tags from above.
|
||||
|
||||
This image was created to be the base image for [**tiangolo/uwsgi-nginx-flask**](https://hub.docker.com/r/tiangolo/uwsgi-nginx-flask/) but could be used as the base image for any other (WSGI-based) Python web application, like Django.
|
||||
|
||||
### * Note on performance and features
|
||||
|
||||
If you are starting a new project, you might benefit from a newer and faster framework based on ASGI instead of WSGI (Flask and Django are WSGI-based).
|
||||
|
||||
You could use an ASGI framework like:
|
||||
|
||||
* [**FastAPI**](https://github.com/tiangolo/fastapi) (which is based on Starlette) with this Docker image: [**tiangolo/uvicorn-gunicorn-fastapi**](https://github.com/tiangolo/uvicorn-gunicorn-fastapi-docker).
|
||||
* [**Starlette**](https://github.com/encode/starlette) directly, with this Docker image: [**tiangolo/uvicorn-gunicorn-starlette**](https://github.com/tiangolo/uvicorn-gunicorn-starlette-docker).
|
||||
* Or any other ASGI framework with this Docker image: [**tiangolo/uvicorn-gunicorn**](https://github.com/tiangolo/uvicorn-gunicorn-docker).
|
||||
|
||||
FastAPI, or Starlette, would give you about 800% (8x) the performance achievable with this image (**tiangolo/uwsgi-nginx**). [You can see the third-party benchmarks here](https://www.techempower.com/benchmarks/#section=test&runid=a979de55-980d-4721-a46f-77298b3f3923&hw=ph&test=query&l=z8kflr-v&a=2).
|
||||
|
||||
Also, if you want to use new technologies like WebSockets it would be easier (and *possible*) with a newer framework based on ASGI, like FastAPI or Starlette. As the standard ASGI was designed to be able to handle asynchronous code like the one needed for WebSockets.
|
||||
|
||||
#### If you need a WSGI-based application (like Flask or Django)
|
||||
|
||||
If you need to use an older WSGI-based framework like Flask or Django (instead of something based on ASGI) and you need to have the best performance possible, you can use the alternative image: [**tiangolo/meinheld-gunicorn**](https://github.com/tiangolo/meinheld-gunicorn-docker).
|
||||
|
||||
**tiangolo/meinheld-gunicorn** will give you about 400% (4x) the performance of this image.
|
||||
|
||||
---
|
||||
|
||||
**GitHub repo**: [https://github.com/tiangolo/uwsgi-nginx-docker](https://github.com/tiangolo/uwsgi-nginx-docker)
|
||||
|
||||
**Docker Hub image**: [https://hub.docker.com/r/tiangolo/uwsgi-nginx/](https://hub.docker.com/r/tiangolo/uwsgi-nginx/)
|
||||
|
||||
## How to use
|
||||
|
||||
* You shouldn't have to clone the GitHub repo. You should use it as a base image for other images, using this in your `Dockerfile`:
|
||||
|
||||
```Dockerfile
|
||||
FROM tiangolo/uwsgi-nginx:python3.8
|
||||
|
||||
# Your Dockerfile code...
|
||||
```
|
||||
|
||||
* But, if you need Python 2.7 that line would have to be `FROM tiangolo/uwsgi-nginx:python2.7`.
|
||||
|
||||
* By default it will try to find a uWSGI config file in `/app/uwsgi.ini`.
|
||||
|
||||
* That `uwsgi.ini` file will make it try to run a Python file in `/app/main.py`.
|
||||
|
||||
If you are building a **Flask** web application you should use instead [**tiangolo/uwsgi-nginx-flask**](https://hub.docker.com/r/tiangolo/uwsgi-nginx-flask/).
|
||||
|
||||
## Advanced usage
|
||||
|
||||
### Custom app directory
|
||||
|
||||
If you need to use a directory for your app different than `/app`, you can override the uWSGI config file path with an environment variable `UWSGI_INI`, and put your custom `uwsgi.ini` file there.
|
||||
|
||||
For example, if you needed to have your application directory in `/application` instead of `/app`, your `Dockerfile` would look like:
|
||||
|
||||
```Dockerfile
|
||||
FROM tiangolo/uwsgi-nginx:python3.8
|
||||
|
||||
ENV UWSGI_INI /application/uwsgi.ini
|
||||
|
||||
COPY ./application /application
|
||||
WORKDIR /appapplication
|
||||
```
|
||||
|
||||
And your `uwsgi.ini` file in `./application/uwsgi.ini` would contain:
|
||||
|
||||
```ini
|
||||
[uwsgi]
|
||||
wsgi-file=/application/main.py
|
||||
```
|
||||
|
||||
**Note**: it's important to include the `WORKDIR` option, otherwise uWSGI will start the application in `/app`.
|
||||
|
||||
### Custom uWSGI process number
|
||||
|
||||
By default, the image starts with 2 uWSGI processes running. When the server is experiencing a high load, it creates up to 16 uWSGI processes to handle it on demand.
|
||||
|
||||
If you need to configure these numbers you can use environment variables.
|
||||
|
||||
The starting number of uWSGI processes is controlled by the variable `UWSGI_CHEAPER`, by default set to `2`.
|
||||
|
||||
The maximum number of uWSGI processes is controlled by the variable `UWSGI_PROCESSES`, by default set to `16`.
|
||||
|
||||
Have in mind that `UWSGI_CHEAPER` must be lower than `UWSGI_PROCESSES`.
|
||||
|
||||
So, if, for example, you need to start with 4 processes and grow to a maximum of 64, your `Dockerfile` could look like:
|
||||
|
||||
```Dockerfile
|
||||
FROM tiangolo/uwsgi-nginx:python3.8
|
||||
|
||||
ENV UWSGI_CHEAPER 4
|
||||
ENV UWSGI_PROCESSES 64
|
||||
|
||||
COPY ./app /app
|
||||
```
|
||||
|
||||
### Custom max upload size
|
||||
|
||||
In this image, Nginx is configured to allow unlimited upload file sizes. This is done because by default a simple Python server would allow that, so that's the simplest behavior a developer would expect.
|
||||
|
||||
If you need to restrict the maximum upload size in Nginx, you can add an environment variable `NGINX_MAX_UPLOAD` and assign a value corresponding to the [standard Nginx config `client_max_body_size`](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size).
|
||||
|
||||
For example, if you wanted to set the maximum upload file size to 1 MB (the default in a normal Nginx installation), you would need to set the `NGINX_MAX_UPLOAD` environment variable to the value `1m`. Then the image would take care of adding the corresponding configuration file (this is done by the `entrypoint.sh`).
|
||||
|
||||
So, your `Dockerfile` would look something like:
|
||||
|
||||
```Dockerfile
|
||||
FROM tiangolo/uwsgi-nginx:python3.8
|
||||
|
||||
ENV NGINX_MAX_UPLOAD 1m
|
||||
|
||||
COPY ./app /app
|
||||
```
|
||||
|
||||
### Custom listen port
|
||||
|
||||
By default, the container made from this image will listen on port 80.
|
||||
|
||||
To change this behavior, set the `LISTEN_PORT` environment variable.
|
||||
|
||||
You might also need to create the respective `EXPOSE` Docker instruction.
|
||||
|
||||
You can do that in your `Dockerfile`, it would look something like:
|
||||
|
||||
```Dockerfile
|
||||
FROM tiangolo/uwsgi-nginx:python3.8
|
||||
|
||||
ENV LISTEN_PORT 8080
|
||||
|
||||
EXPOSE 8080
|
||||
|
||||
COPY ./app /app
|
||||
```
|
||||
|
||||
### Custom `/app/prestart.sh`
|
||||
|
||||
If you need to run anything before starting the app, you can add a file `prestart.sh` to the directory `/app`. The image will automatically detect and run it before starting everything.
|
||||
|
||||
For example, if you want to add database migrations that are run on startup (e.g. with Alembic, or Django migrations), before starting the app, you could create a `./app/prestart.sh` file in your code directory (that will be copied by your `Dockerfile`) with:
|
||||
|
||||
```bash
|
||||
#! /usr/bin/env bash
|
||||
|
||||
# Let the DB start
|
||||
sleep 10;
|
||||
# Run migrations
|
||||
alembic upgrade head
|
||||
```
|
||||
|
||||
and it would wait 10 seconds to give the database some time to start and then run that `alembic` command (you could update that to run Django migrations or any other tool you need).
|
||||
|
||||
If you need to run a Python script before starting the app, you could make the `/app/prestart.sh` file run your Python script, with something like:
|
||||
|
||||
```bash
|
||||
#! /usr/bin/env bash
|
||||
|
||||
# Run custom Python script before starting
|
||||
python /app/my_custom_prestart_script.py
|
||||
```
|
||||
|
||||
**Note**: The image uses `.` to run the script (as in `. /app/prestart.sh`), so for example, environment variables would persist. If you don't understand the previous sentence, you probably don't need it.
|
||||
|
||||
### Custom Nginx processes number
|
||||
|
||||
By default, Nginx will start one "worker process".
|
||||
|
||||
If you want to set a different number of Nginx worker processes you can use the environment variable `NGINX_WORKER_PROCESSES`.
|
||||
|
||||
You can use a specific single number, e.g.:
|
||||
|
||||
```Dockerfile
|
||||
ENV NGINX_WORKER_PROCESSES 2
|
||||
```
|
||||
|
||||
or you can set it to the keyword `auto` and it will try to autodetect the number of CPUs available and use that for the number of workers.
|
||||
|
||||
For example, using `auto`, your Dockerfile could look like:
|
||||
|
||||
```Dockerfile
|
||||
FROM tiangolo/uwsgi-nginx:python3.8
|
||||
|
||||
ENV NGINX_WORKER_PROCESSES auto
|
||||
|
||||
COPY ./app /app
|
||||
```
|
||||
|
||||
### Custom Nginx maximum connections per worker
|
||||
|
||||
By default, Nginx will start with a maximum limit of 1024 connections per worker.
|
||||
|
||||
If you want to set a different number you can use the environment variable `NGINX_WORKER_CONNECTIONS`, e.g:
|
||||
|
||||
```Dockerfile
|
||||
ENV NGINX_WORKER_CONNECTIONS 2048
|
||||
```
|
||||
|
||||
It cannot exceed the current limit on the maximum number of open files. See how to configure it in the next section.
|
||||
|
||||
### Custom Nginx maximum open files
|
||||
|
||||
The number connections per Nginx worker cannot exceed the limit on the maximum number of open files.
|
||||
|
||||
You can change the limit of open files with the environment variable `NGINX_WORKER_OPEN_FILES`, e.g.:
|
||||
|
||||
```Dockerfile
|
||||
ENV NGINX_WORKER_OPEN_FILES 2048
|
||||
```
|
||||
|
||||
### Customizing Nginx additional configurations
|
||||
|
||||
If you need to configure Nginx further, you can add `*.conf` files to `/etc/nginx/conf.d/` in your `Dockerfile`.
|
||||
|
||||
Just have in mind that the default configurations are created during startup in a file at `/etc/nginx/conf.d/nginx.conf` and `/etc/nginx/conf.d/upload.conf`. So you shouldn't overwrite them. You should name your `*.conf` file with something different than `nginx.conf` or `upload.conf`, for example: `custom.conf`.
|
||||
|
||||
**Note**: if you are customizing Nginx, maybe copying configurations from a blog or a StackOverflow answer, have in mind that you probably need to use the [configurations specific to uWSGI](http://nginx.org/en/docs/http/ngx_http_uwsgi_module.html), instead of those for other modules, like for example, `ngx_http_fastcgi_module`.
|
||||
|
||||
### Overriding Nginx configuration completely
|
||||
|
||||
If you need to configure Nginx even further, completely overriding the defaults, you can add a custom Nginx configuration to `/app/nginx.conf`.
|
||||
|
||||
It will be copied to `/etc/nginx/nginx.conf` and used instead of the generated one.
|
||||
|
||||
Have in mind that, in that case, this image won't generate any of the Nginx configurations, it will only copy and use your configuration file.
|
||||
|
||||
That means that all the environment variables described above that are specific to Nginx won't be used.
|
||||
|
||||
It also means that it won't use additional configurations from files in `/etc/nginx/conf.d/*.conf`, unless you explicitly have a section in your custom file `/app/nginx.conf` with:
|
||||
|
||||
```conf
|
||||
include /etc/nginx/conf.d/*.conf;
|
||||
```
|
||||
|
||||
If you want to add a custom `/app/nginx.conf` file but don't know where to start from, you can use [the `nginx.conf` used for the tests](https://github.com/tiangolo/uwsgi-nginx-docker/blob/master/tests/test_02_app/custom_nginx_app/app/nginx.conf) and customize it or modify it further.
|
||||
|
||||
## Technical details
|
||||
|
||||
The combination of uWSGI with Nginx is a [common way to deploy Python web applications](http://flask.pocoo.org/docs/1.0/deploying/uwsgi/).
|
||||
|
||||
Roughly:
|
||||
|
||||
* **Nginx** is a web server, it takes care of the HTTP connections and also can serve static files directly and more efficiently.
|
||||
|
||||
* **uWSGI** is an application server, that's what runs your Python code and it talks with Nginx.
|
||||
|
||||
* **Your Python code** has the actual web application, and is run by uWSGI.
|
||||
|
||||
This image takes advantage of already slim and optimized existing Docker images (based on Debian as [recommended by Docker](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/)) and implements Docker best practices.
|
||||
|
||||
It uses the official Python Docker image, installs uWSGI and on top of that, with the least amount of modifications, adds the official Nginx image (as of 2016-02-14).
|
||||
|
||||
And it controls all these processes with Supervisord.
|
||||
|
||||
---
|
||||
|
||||
There's the rule of thumb that you should have "one process per container".
|
||||
|
||||
That helps, for example, isolating an app and its database in different containers.
|
||||
|
||||
But if you want to have a "micro-services" approach you may want to [have more than one process in one container](https://valdhaus.co/writings/docker-misconceptions/) if they are all related to the same "service", and you may want to include your Flask code, uWSGI and Nginx in the same container (and maybe run another container with your database).
|
||||
|
||||
That's the approach taken in this image.
|
||||
|
||||
---
|
||||
|
||||
This image has a default sample "Hello World" app in the container's `/app` directory using the example in the [uWSGI documentation](http://uwsgi-docs.readthedocs.org/en/latest/WSGIquickstart.html).
|
||||
|
||||
You probably want to override it or delete it in your project.
|
||||
|
||||
It is there in case you run this image by itself and not as a base image for your own `Dockerfile`, so that you get a sample app without errors.
|
||||
|
||||
## Tests
|
||||
|
||||
All the image tags, configurations, environment variables and application options are tested.
|
||||
|
||||
## Updates
|
||||
|
||||
Updates are announced in the releases.
|
||||
|
||||
You can click the "watch" button at the top right and select "Releases only" to receive an email notification when there's a new release.
|
||||
|
||||
## Release Notes
|
||||
|
||||
### Latest Changes
|
||||
|
||||
* 🐛 Fix broken link to TechEmpower benchmarks. PR [#96](https://github.com/tiangolo/uwsgi-nginx-docker/pull/96) by [@tiangolo](https://github.com/tiangolo).
|
||||
* 👷 Add GitHub Action latest-changes, update issue-manager. PR [#92](https://github.com/tiangolo/uwsgi-nginx-docker/pull/92) by [@tiangolo](https://github.com/tiangolo).
|
||||
* Fix Python 3.8 Alpine environment for installed packages. PR [#84](https://github.com/tiangolo/uwsgi-nginx-docker/pull/84).
|
||||
|
||||
### 1.4.0
|
||||
|
||||
* Add [GitHub Sponsors](https://github.com/sponsors/tiangolo) button.
|
||||
* Add new image for Python 3.8, and new image for Python 3.8 on Alpine. PR [#83](https://github.com/tiangolo/uwsgi-nginx-docker/pull/83).
|
||||
* Upgrade Nginx to latest version, `1.17.10`, based on latest Debian, Buster. PR [#82](https://github.com/tiangolo/uwsgi-nginx-docker/pull/82).
|
||||
* Remove support for Python 3.5. PR [#81](https://github.com/tiangolo/uwsgi-nginx-docker/pull/81).
|
||||
|
||||
### 1.3.0
|
||||
|
||||
* This is the last version to support:
|
||||
* Debian Stretch (before upgrading to Buster).
|
||||
* Python 3.5.
|
||||
* Alpine 3.7, 3.8, 3.9 (before upgrading to Alpine 3.11).
|
||||
* Alpine in older versions of Python, 2.7 and 3.6 (Before upgrading to Python 3.8).
|
||||
* If you need any of those, make sure to use a tag for the build date `2020-05-04`.
|
||||
* Refactor build set up:
|
||||
* Re-use code and configs.
|
||||
* Migrate to GitHub Actions.
|
||||
* Simplify tests.
|
||||
* PR [#78](https://github.com/tiangolo/uwsgi-nginx-docker/pull/78).
|
||||
* Migrate Travis to .com, update badge. PR [#77](https://github.com/tiangolo/uwsgi-nginx-docker/pull/77).
|
||||
|
||||
### 1.2.0
|
||||
|
||||
* 2019-10-14:
|
||||
* Refactor and simplify test scripts. PR [#66](https://github.com/tiangolo/uwsgi-nginx-docker/pull/66).
|
||||
* 2019-09-28:
|
||||
* Refactor build scripts and add image tags for each build date, like `tiangolo/uwsgi-nginx:python3.7-2019-09-28`. PR [#65](https://github.com/tiangolo/uwsgi-nginx-docker/pull/65).
|
||||
|
||||
* Upgrade Travis. PR [#60](https://github.com/tiangolo/uwsgi-nginx-docker/pull/60).
|
||||
|
||||
### 1.1.0
|
||||
|
||||
* Added support for `/app/prestart.sh` script to run arbitrary code before starting the app (for example, Alembic - SQLAlchemy migrations). The [documentation for the `/app/prestart.sh` is in the main README](https://github.com/tiangolo/uwsgi-nginx-docker#custom-appprestartsh). [PR #59](https://github.com/tiangolo/uwsgi-nginx-docker/pull/59).
|
||||
|
||||
### 1.0.0
|
||||
|
||||
* 2019-05-04:
|
||||
* Add Alpine Linux 3.9. PR [#55](https://github.com/tiangolo/uwsgi-nginx-docker/pull/55) by [evilgoldfish](https://github.com/evilgoldfish).
|
||||
* Build images using Travis matrix to improve development/testing speed. Needed for some recent PRs. [PR #58](https://github.com/tiangolo/uwsgi-nginx-docker/pull/58).
|
||||
|
||||
* 2019-02-02:
|
||||
* The Nginx configurations are generated dynamically from the entrypoint, instead of modifying pre-existing files. [PR #50](https://github.com/tiangolo/uwsgi-nginx-docker/pull/50).
|
||||
* Support for a completely custom `/app/nginx.conf` file that overrides the generated one. [PR #51](https://github.com/tiangolo/uwsgi-nginx-docker/pull/51).
|
||||
|
||||
* 2018-11-23: New Alpine 3.8 images for Python 2.7, Python 3.6 and Python 3.7 (Python 3.7 temporarily disabled). Thanks to [philippfreyer](https://github.com/philippfreyer) in [PR #45](https://github.com/tiangolo/uwsgi-nginx-docker/pull/45)
|
||||
|
||||
* 2018-09-22: New Python 3.7 versions, standard and Alpine based. Thanks to [desaintmartin](https://github.com/desaintmartin) in [this PR](https://github.com/tiangolo/uwsgi-nginx-docker/pull/39).
|
||||
|
||||
* 2018-06-22: You can now use `NGINX_WORKER_CONNECTIONS` to set the maximum number of Nginx worker connections and `NGINX_WORKER_OPEN_FILES` to set the maximum number of open files. Thanks to [ronlut](https://github.com/ronlut) in [this PR](https://github.com/tiangolo/uwsgi-nginx-docker/pull/26).
|
||||
|
||||
* 2018-06-22: Make uWSGI require an app to run, instead of going in "full dynamic mode" while there was an error. Supervisord doesn't terminate itself but tries to restart uWSGI and shows the errors. Uses `need-app` as suggested by [luckydonald](https://github.com/luckydonald) in [this comment](https://github.com/tiangolo/uwsgi-nginx-flask-docker/issues/3#issuecomment-321991279).
|
||||
|
||||
* 2018-06-22: Correctly handled graceful shutdown of uWSGI and Nginx. Thanks to [desaintmartin](https://github.com/desaintmartin) in [this PR](https://github.com/tiangolo/uwsgi-nginx-docker/pull/30).
|
||||
|
||||
* 2018-02-04: It's now possible to set the number of Nginx worker processes with the environment variable `NGINX_WORKER_PROCESSES`. Thanks to [naktinis](https://github.com/naktinis) in [this PR](https://github.com/tiangolo/uwsgi-nginx-docker/pull/22).
|
||||
|
||||
* 2018-01-14: There are now two Alpine based versions, `python2.7-alpine3.7` and `python3.6-alpine3.7`.
|
||||
|
||||
* 2017-12-08: Now you can configure which port the container should listen on, using the environment variable `LISTEN_PORT` thanks to [tmshn](https://github.com/tmshn) in [this PR](https://github.com/tiangolo/uwsgi-nginx-docker/pull/16).
|
||||
|
||||
* 2017-08-09: You can set a custom maximum upload file size using an environment variable `NGINX_MAX_UPLOAD`, by default it has a value of `0`, that allows unlimited upload file sizes. This differs from Nginx's default value of 1 MB. It's configured this way because that's the simplest experience a developer that is not expert in Nginx would expect.
|
||||
|
||||
* 2017-08-09: Now you can override where to look for the `uwsgi.ini` file, and with that, change the default directory from `/app` to something else, using the envirnoment variable `UWSGI_INI`.
|
||||
|
||||
* 2017-08-08: There's a new `latest` tag image, just to show a warning for those still using `latest` for Python 2.7 web applications. As of now, [everyone](https://www.python.org/dev/peps/pep-0373/) [should be](http://flask.pocoo.org/docs/0.12/python3/#python3-support) [using Python 3](https://docs.djangoproject.com/en/1.11/faq/install/#what-python-version-should-i-use-with-django).
|
||||
|
||||
* 2017-08-08: Supervisord now terminates uWSGI on `SIGTERM`, so if you run `docker stop` or something similar, it will actually stop everything, instead of waiting for Docker's timeout to kill the container.
|
||||
|
||||
* 2017-07-31: There's now an image tag for Python 3.6, based on the official image for Python 3.6 thanks to [jrd](https://github.com/jrd) in [this PR](https://github.com/tiangolo/uwsgi-nginx-docker/pull/6).
|
||||
|
||||
* 2016-10-01: Now you can override default `uwsgi.ini` parameters from the file in `/app/uwsgi.ini`.
|
||||
|
||||
* 2016-08-16: There's now an image tag for Python 3.5, based on the official image for Python 3.5. So now you can use this image for your projects in Python 2.7 and Python 3.5.
|
||||
|
||||
* 2016-08-16: Use dynamic a number of worker processes for uWSGI, from 2 to 16 depending on load. This should work for most cases. This helps especially when there are some responses that are slow and take some time to be generated, this change allows all the other responses to keep fast (in a new process) without having to wait for the first (slow) one to finish.
|
||||
|
||||
* Also, it now uses a base `uwsgi.ini` file under `/etc/uwsgi/` with most of the general configurations, so, the `uwsgi.ini` inside `/app` (the one you could need to modify) is now a lot simpler.
|
||||
|
||||
* 2016-04-05: Nginx and uWSGI logs are now redirected to stdout, allowing to use `docker logs`.
|
||||
|
||||
## License
|
||||
|
||||
This project is licensed under the terms of the Apache license.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,9 @@
|
|||
# vnstat-dashboard for docker
|
||||
# vnstat-dashboard
|
||||
|
||||
GitHub [stilleshan/dockerfile](https://github.com/stilleshan/dockerfile)
|
||||
GitHub [stilleshan/dockerfiles](https://github.com/stilleshan/dockerfiles)
|
||||
Docker [stilleshan/vnstat-dashboard](https://hub.docker.com/r/stilleshan/vnstat-dashboard)
|
||||
> *docker image support for X86 and ARM*
|
||||
|
||||
## 使用
|
||||
本仓库参考 [tomangert/vnstat-dashboard](https://github.com/tomangert/vnstat-dashboard) 对原作者仓库 [alexandermarston/vnstat-dashboard](https://github.com/alexandermarston/vnstat-dashboard) 进行部分 bug 修复后构建 docker 镜像,主要用与自用和存档备份,具体使用教程请参考原作者仓库`README`文件.
|
||||
本仓库参考 [tomangert/vnstat-dashboard](https://github.com/tomangert/vnstat-dashboard) 对原作者仓库 [alexandermarston/vnstat-dashboard](https://github.com/alexandermarston/vnstat-dashboard) 进行部分 bug 修复后构建 X86 和 ARM 平台 docker 镜像,具体使用教程请参考原作者仓库.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue