Skip to content
Snippets Groups Projects
Commit 0e8e4c28 authored by drpsyko101's avatar drpsyko101
Browse files

Update image tags

* add lint-test instructions
* fix auth api not starting without API_EXTERNAL_URL
* remove redundant kong ingress service
parent 92a2576e
No related branches found
No related tags found
No related merge requests found
......@@ -217,6 +217,13 @@ kong:
Before creating a merge request, you can test the charts locally by using [helm/chart-testing](https://github.com/helm/chart-testing). If you have Docker and a Kubernetes environment to test with, simply run:
```shell
# Run chart-testing (lint)
docker run -it \
--workdir=/data \
--volume $(pwd)/charts/supabase:/data \
quay.io/helmpack/chart-testing:v3.7.1 \
ct lint --validate-maintainers=false --chart-dirs . --charts .
# Run chart-testing (install)
docker run -it \
--network host \
--workdir=/data \
......@@ -230,7 +237,7 @@ docker run -it \
#### `0.0.x` to `0.1.x`
* `supabase/postgres` bumped from `14.1` to `15.1`, which warrants backing up all your data before proceeding to update major version
* `supabase/postgres` is updated from `14.1` to `15.1`, which warrants backing up all your data before proceeding to update to the next major version.
* Intialization scripts for `supabase/postgres` has been reworked and matched closely to the [Docker Compose](https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml) version. Further tweaks to the scripts are needed to ensure backward-compatibility.
* Migration scripts are now exposed at `db.config`, which will be mounted at `/docker-entrypoint-initdb.d/migrations/`. Simply copy your migration files from your local project's `supabase/migration` and populate the `db.config`.
* Ingress are now limited to `kong` & `db` services. This is by design to limit entry to the stack through secure `kong` service.
......
......@@ -20,7 +20,7 @@ db:
enabled: true
image:
repository: supabase/postgres
tag: 15.1.0.117
tag: 15.1.0.147
livenessProbe:
exec:
command:
......@@ -50,6 +50,7 @@ auth:
image:
tag: v2.125.1
environment:
API_EXTERNAL_URL: http://example.com
GOTRUE_SITE_URL: http://example.com
GOTRUE_EXTERNAL_EMAIL_ENABLED: "true"
GOTRUE_MAILER_AUTOCONFIRM: "true"
......@@ -60,7 +61,7 @@ auth:
rest:
image:
tag: v11.2.2
tag: v12.0.1
realtime:
image:
......@@ -121,9 +122,6 @@ kong:
paths:
- path: /
pathType: Prefix
backend:
serviceName: api
servicePort: 80
analytics:
image:
......
......@@ -167,7 +167,7 @@ studio:
STUDIO_DEFAULT_ORGANIZATION: Default Organization
STUDIO_DEFAULT_PROJECT: Default Project
STUDIO_PORT: "3000"
SUPABASE_PUBLIC_URL: http://EXAMPLE.COM/
SUPABASE_PUBLIC_URL: http://example.com
NEXT_PUBLIC_ENABLE_LOGS: "true"
# volumeMounts:
# - name: volume_name
......@@ -243,9 +243,10 @@ auth:
DB_PORT: 5432
DB_DRIVER: postgres
DB_SSL: disable # disable, allow, prefer, require, verify-ca, verify-full
API_EXTERNAL_URL: http://example.com
GOTRUE_API_HOST: "0.0.0.0"
GOTRUE_API_PORT: "9999"
GOTRUE_SITE_URL: https://STUDIO.EXAMPLE.COM
GOTRUE_SITE_URL: http://example.com
GOTRUE_URI_ALLOW_LIST: "*"
GOTRUE_DISABLE_SIGNUP: "false"
GOTRUE_JWT_DEFAULT_GROUP_NAME: authenticated
......@@ -750,18 +751,18 @@ kong:
nginx.ingress.kubernetes.io/rewrite-target: /
# cert-manager.io/cluster-issuer: "letsencrypt-staging"
# kubernetes.io/tls-acme: "true"
tls:
- secretName: API.EXAMPLE.COM
tls: []
# Define TLS secret for SSL termination.
# This section can be left blank if using cluster certificate manager.
# Otherwise, setting this in tandem with certificate manager will overwrite the secret name.
# - secretName: example-com-tls
# hosts:
# - example.com
hosts:
- API.EXAMPLE.COM
hosts:
- host: API.EXAMPLE.COM
- host: example.com
paths:
- path: /
pathType: Prefix
backend:
serviceName: api
servicePort: 80
# volumeMounts:
# - name: volume_name
# mountPath: /path/to/my/secret
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment