mirror of https://github.com/supernets/LibreY.git
fix(instances.json): fixing order; feat: add watchtower to automatically pull newest image upon release (merge pull request #38 from codedipper/watchtower)
watchtower, fix instances.json order
This commit is contained in:
commit
2ed2370219
|
@ -1,4 +1,4 @@
|
|||
version: "2.1"
|
||||
version: "3"
|
||||
services:
|
||||
librey:
|
||||
image: ghcr.io/ahwxorg/librey:latest
|
||||
|
@ -21,3 +21,7 @@ services:
|
|||
- ./nginx_logs:/var/log/nginx
|
||||
- ./php_logs:/var/log/php7
|
||||
restart: unless-stopped
|
||||
watchtower:
|
||||
image: containrrr/watchtower
|
||||
volumes:
|
||||
- /var/run/docker.sock:/var/run/docker.sock
|
||||
|
|
|
@ -34,12 +34,20 @@ docker run -d \
|
|||
ghcr.io/ahwxorg/librey:latest
|
||||
```
|
||||
|
||||
Also run with watchtower for auto-updating: (optional)
|
||||
```sh
|
||||
docker run -d \
|
||||
--name librey-watchtower-1 \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower
|
||||
```
|
||||
|
||||
<br>
|
||||
|
||||
### Running a Docker container with composer
|
||||
|
||||
```yml
|
||||
version: "2.1"
|
||||
version: "3"
|
||||
services:
|
||||
librey:
|
||||
image: ghcr.io/ahwxorg/librey:latest
|
||||
|
@ -62,6 +70,10 @@ services:
|
|||
- ./nginx_logs:/var/log/nginx
|
||||
- ./php_logs:/var/log/php7
|
||||
restart: unless-stopped
|
||||
watchtower:
|
||||
image: containrrr/watchtower
|
||||
volumes:
|
||||
- /var/run/docker.sock:/var/run/docker.sock
|
||||
```
|
||||
|
||||
<br>
|
||||
|
@ -179,7 +191,7 @@ docker build -t librey:latest .
|
|||
|
||||
Supported architectures for the official librey images include the same ones supported by Alpine itself, which are typically denoted as `linux/386`, `linux/amd64`, `linux/arm/v6`. If you need support for a different architecture, such as `linux/arm/v7`, you can modify the 'Dockerfile' to use a more comprehensive base image like `ubuntu:latest` instead.
|
||||
|
||||
In this case, you must run the `build` process specifying the desired architecture as shown in the example below:
|
||||
In this case, you must run the `buildx` process specifying the desired architecture as shown in the example below:
|
||||
|
||||
```sh
|
||||
docker buildx build \
|
||||
|
|
|
@ -29,16 +29,16 @@
|
|||
"librey": true
|
||||
},
|
||||
{
|
||||
"clearnet": "https://librey.org/",
|
||||
"tor": "http://jxhkfulu6wpdl4apuy4dyivuowmpprvsd7e3el2z73crq7fmyv7rjkyd.onion/",
|
||||
"i2p": null,
|
||||
"clearnet": "https://lx.vern.cc/",
|
||||
"tor": "http://lx.vernccvbvyi5qhfzyqengccj7lkove6bjot2xhh5kajhwvidqafczrad.onion/",
|
||||
"i2p": "http://vernziqfqvweijfaacmwazohgpdo2bt2ib2jlupt2pwwu27bhgxq.b32.i2p/",
|
||||
"country": "US",
|
||||
"librey": true
|
||||
},
|
||||
{
|
||||
"clearnet": "https://lx.vern.cc/",
|
||||
"tor": "http://lx.vernccvbvyi5qhfzyqengccj7lkove6bjot2xhh5kajhwvidqafczrad.onion/",
|
||||
"i2p": "http://vernziqfqvweijfaacmwazohgpdo2bt2ib2jlupt2pwwu27bhgxq.b32.i2p/",
|
||||
"clearnet": "https://librey.org/",
|
||||
"tor": "http://jxhkfulu6wpdl4apuy4dyivuowmpprvsd7e3el2z73crq7fmyv7rjkyd.onion/",
|
||||
"i2p": null,
|
||||
"country": "US",
|
||||
"librey": true
|
||||
},
|
||||
|
|
Loading…
Reference in New Issue