diff --git a/README.md b/README.md index 58a88523..b6b45751 100644 --- a/README.md +++ b/README.md @@ -20,8 +20,7 @@
-
-
+
@@ -102,7 +101,7 @@ Deploy production ready Authorizer instance using one click deployment options a
| Railway.app | [](https://railway.com/deploy/nwXp1C?referralCode=FEF4uT&utm_medium=integration&utm_source=template&utm_campaign=generic) | [docs](https://docs.authorizer.dev/deployment/railway) |
| Heroku |
| [docs](https://docs.authorizer.dev/deployment/heroku) |
| Render | [](https://render.com/deploy?repo=https://github.com/authorizerdev/authorizer-render) | [docs](https://docs.authorizer.dev/deployment/render) |
-| Koyeb |
| [docs](https://docs.authorizer.dev/deployment/koyeb) |
+| Koyeb |
| [docs](https://docs.authorizer.dev/deployment/koyeb) |
| RepoCloud |
| [docs](https://repocloud.io/details/?app_id=174) |
| Alibaba Cloud| | [docs](https://docs.authorizer.dev/deployment/alibaba-cloud) |
@@ -146,7 +145,7 @@ The default image runs as **non-root** (UID `65532`). Writable mounts (SQLite un
```sh
docker run -p 8080:8080 -u root \
-v authorizer_data:/authorizer/data \
- lakhansamani/authorizer \
+ quay.io/authorizer/authorizer \
--database-type=sqlite \
--database-url=/authorizer/data/data.db \
--client-id=123456 \
@@ -162,7 +161,7 @@ The default image runs as **non-root** (UID `65532`). Writable mounts (SQLite un
mkdir -p ./data && sudo chown -R 65532:65532 ./data
docker run -p 8080:8080 \
-v "$(pwd)/data:/authorizer/data" \
- lakhansamani/authorizer \
+ quay.io/authorizer/authorizer \
--database-type=sqlite \
--database-url=/authorizer/data/data.db \
...
@@ -187,7 +186,7 @@ Inside a container, **`localhost` / `127.0.0.1` is the container itself**, not y
- **Docker Desktop (macOS / Windows):** use `host.docker.internal` in `--database-url` or `--database-host` (built in).
```sh
- docker run -p 8080:8080 lakhansamani/authorizer \
+ docker run -p 8080:8080 quay.io/authorizer/authorizer \
--database-type=postgres \
--database-url="postgres://user:pass@host.docker.internal:5432/dbname?sslmode=disable" \
...
@@ -197,7 +196,7 @@ Inside a container, **`localhost` / `127.0.0.1` is the container itself**, not y
```sh
docker run -p 8080:8080 --add-host=host.docker.internal:host-gateway \
- lakhansamani/authorizer \
+ quay.io/authorizer/authorizer \
--database-type=postgres \
--database-url="postgres://user:pass@host.docker.internal:5432/dbname?sslmode=disable" \
...
@@ -207,10 +206,10 @@ Inside a container, **`localhost` / `127.0.0.1` is the container itself**, not y
Ensure the database accepts **non-localhost** connections (e.g. `listen_addresses` in Postgres, bind address in MySQL) and that your OS firewall allows the Docker subnet.
-**Extending the image with env-based config (e.g. Railway):** If you `FROM lakhansamani/authorizer` and use a shell-form `CMD` so that env vars are expanded at runtime, you must override `ENTRYPOINT` in your Dockerfile or the binary will receive `/bin/sh` and `-c` as arguments and fail. Use:
+**Extending the image with env-based config (e.g. Railway):** If you `FROM quay.io/authorizer/authorizer` and use a shell-form `CMD` so that env vars are expanded at runtime, you must override `ENTRYPOINT` in your Dockerfile or the binary will receive `/bin/sh` and `-c` as arguments and fail. Use:
```dockerfile
-FROM lakhansamani/authorizer:2.0.0-rc.1
+FROM quay.io/authorizer/authorizer:2.0.0-rc.1
# v2 uses CLI arguments only. Railway (etc.) inject env vars; shell form CMD expands them at runtime.
# Override ENTRYPOINT so CMD is run by a shell; otherwise the base ENTRYPOINT would receive /bin/sh -c "..." as args.
ENTRYPOINT ["/bin/sh", "-c"]