Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

correct misleading description of WITH_NO_RESOLVE_IMAGE #100

Merged
merged 1 commit into from
Jul 24, 2023
Merged

correct misleading description of WITH_NO_RESOLVE_IMAGE #100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,9 +89,9 @@ You also need to add a label `shepherd.auth.config` to the container to be updat
- shepherd.auth.config=blog
```

You can enable connection to insecure private registry by setting the `WITH_INSECURE_REGISTRY` variable.
You can enable connection to insecure private registry by setting the `WITH_INSECURE_REGISTRY` variable to `true`.

You can force image deployment whatever the architecture by setting the `WITH_NO_RESOLVE_IMAGE` variable.
You can prevent pulling images from the registry by setting the `WITH_NO_RESOLVE_IMAGE` variable to `true`.

You can enable notifications on service update with apprise, using the [apprise microservice](https://github.com/djmaze/apprise-microservice) and the `APPRISE_SIDECAR_URL` variable. See the file [docker-compose.apprise.yml](examples/docker-compose.apprise.yml) for an example.

Expand Down