Compare commits

..

No commits in common. "ea87d67b75679c93496085265ec6ca51043658ca" and "c216fb1430805269f3bcd0aa56be1a83c180a6d8" have entirely different histories.

4 changed files with 9 additions and 9 deletions

View file

@ -50,7 +50,7 @@ In order to run Zerobyte, you need to have Docker and Docker Compose installed o
```yaml
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.35
container_name: zerobyte
restart: unless-stopped
cap_add:
@ -134,7 +134,7 @@ If you only need to back up locally mounted folders and don't require remote sha
```yaml
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.35
container_name: zerobyte
restart: unless-stopped
ports:
@ -173,7 +173,7 @@ If you want to track a local directory on the same server where Zerobyte is runn
```diff
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.35
container_name: zerobyte
restart: unless-stopped
cap_add:
@ -248,7 +248,7 @@ Zerobyte can use [rclone](https://rclone.org/) to support 40+ cloud storage prov
```diff
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.35
container_name: zerobyte
restart: unless-stopped
cap_add:

View file

@ -100,7 +100,7 @@ If you run Traefik as your reverse proxy, add labels to the Zerobyte service in
```yaml docker-compose.yml
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.29
container_name: zerobyte
restart: unless-stopped
environment:

View file

@ -52,7 +52,7 @@ Create a `docker-compose.yml` file with the following configuration:
```yaml docker-compose.yml
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.30
container_name: zerobyte
restart: unless-stopped
cap_add:
@ -179,7 +179,7 @@ If you only need to back up locally mounted directories and don't require remote
```yaml docker-compose.yml
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.30
container_name: zerobyte
restart: unless-stopped
ports:
@ -254,7 +254,7 @@ If you use provisioning, Zerobyte can resolve secrets from environment variables
```yaml docker-compose.yml
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.30
container_name: zerobyte
restart: unless-stopped
cap_add:

View file

@ -111,7 +111,7 @@ Update your `docker-compose.yml` to mount the directory you want to backup:
```yaml
services:
zerobyte:
image: ghcr.io/nicotsx/zerobyte:v0.35.0
image: ghcr.io/nicotsx/zerobyte:v0.30
container_name: zerobyte
restart: unless-stopped
# ... other configuration ...