ghcr links instead of build in compose examples in readme

This commit is contained in:
BroodjeAap 2022-12-30 16:13:56 +00:00
parent da651b5fee
commit e3b175c763
2 changed files with 5 additions and 18 deletions

View file

@ -51,10 +51,7 @@ version: "3"
services:
app:
build:
context: .
dockerfile: Dockerfile
target: base
image: ghcr.io/broodjeaap/go-watch:master
container_name: go-watch
environment:
- GOWATCH_DATABASE_DSN=postgres://gorm:gorm@db:5432/gorm
@ -92,10 +89,7 @@ When using the docker image, the `HTTP_PROXY` and `HTTPS_PROXY` environment vari
```
services:
app:
build:
context: .
dockerfile: Dockerfile
target: base
image: ghcr.io/broodjeaap/go-watch:master
container_name: go-watch
environment:
- HTTP_PROXY=http://proxy.com:1234
@ -107,10 +101,7 @@ Proxy 'pools' are not directly supported by Go-Watch, but can still be set up by
```
services:
app:
build:
context: .
dockerfile: Dockerfile
target: base
image: ghcr.io/broodjeaap/go-watch:master
container_name: go-watch
environment:
- HTTP_PROXY=http://squid_proxy:3128
@ -135,10 +126,7 @@ version: "3"
services:
app:
build:
context: .
dockerfile: Dockerfile
target: base
image: ghcr.io/broodjeaap/go-watch:master
container_name: go-watch
environment:
- GOWATCH_DATABASE_DSN=postgres://gorm:gorm@db:5432/gorm

View file

@ -11,5 +11,4 @@
- postgresql
- postgresql+apprise
- postgresql+apprise+browserless
- organize docs?
- replace 'build' keys in compose snippets in readme with direct link
- organize docs?