[bitnami/supabase-storage] Release 0.45.0-debian-11-r0 (#54804)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-01-16 14:59:03 +01:00
committed by GitHub
parent e825455731
commit 293342a68f
5 changed files with 48 additions and 36 deletions

View File

@@ -7,13 +7,13 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2024-01-11T14:39:39Z" \
org.opencontainers.image.created="2024-01-16T13:26:33Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="0.44.1-debian-11-r0" \
org.opencontainers.image.ref.name="0.45.0-debian-11-r0" \
org.opencontainers.image.title="supabase-storage" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="0.44.1"
org.opencontainers.image.version="0.45.0"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -28,7 +28,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \
"python-3.11.7-2-linux-${OS_ARCH}-debian-11" \
"node-18.19.0-0-linux-${OS_ARCH}-debian-11" \
"supabase-storage-0.44.1-0-linux-${OS_ARCH}-debian-11" \
"supabase-storage-0.45.0-0-linux-${OS_ARCH}-debian-11" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -45,7 +45,7 @@ RUN apt-get autoremove --purge -y curl && \
apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives
RUN useradd -r -u 1001 -g root supabase-storage
ENV APP_VERSION="0.44.1" \
ENV APP_VERSION="0.45.0" \
BITNAMI_APP_NAME="supabase-storage" \
PATH="/opt/bitnami/python/bin:/opt/bitnami/node/bin:/opt/bitnami/supabase-storage/node_modules/.bin:$PATH"

View File

@@ -1,8 +0,0 @@
# Copyright VMware, Inc.
# SPDX-License-Identifier: APACHE-2.0
version: '2'
services:
supabase-storage:
image: docker.io/bitnami/supabase-storage:0

View File

@@ -15,6 +15,6 @@
"arch": "amd64",
"distro": "debian-11",
"type": "NAMI",
"version": "0.44.1-0"
"version": "0.45.0-0"
}
}

View File

@@ -1,5 +1,5 @@
rolling-tags:
- "0"
- 0-debian-11
- 0.44.1
- 0.45.0
- latest

View File

@@ -13,13 +13,6 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run -it --name supabase-storage bitnami/supabase-storage
```
### Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/supabase-storage/docker-compose.yml > docker-compose.yml
docker-compose up -d
```
## Why use Bitnami Images?
* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
@@ -73,20 +66,12 @@ Bitnami provides up-to-date versions of Supabase Storage, including security pat
docker pull bitnami/supabase-storage:latest
```
or if you're using Docker Compose, update the value of the image property to `bitnami/supabase-storage:latest`.
#### Step 2: Remove the currently running container
```console
docker rm -v supabase-storage
```
or using Docker Compose:
```console
docker-compose rm -v supabase-storage
```
#### Step 3: Run the new image
Re-create your container from the new image.
@@ -95,14 +80,43 @@ Re-create your container from the new image.
docker run --name supabase-storage bitnami/supabase-storage:latest
```
or using Docker Compose:
```console
docker-compose up supabase-storage
```
## Configuration
### Environment variables
#### Customizable environment variables
| Name | Description | Default Value |
|-----------------------------|------------------------|---------------------------------------------------------------------------|
| `DB_HOST` | Database host | `localhost` |
| `DB_PORT` | Database port number | `5432` |
| `DB_NAME` | Database name | `postgres` |
| `DB_USER` | Database user username | `postgres` |
| `DATABASE_URL` | Database url | `postgresql://${DB_USER}:${DB_PASSWORD}@${DB_HOST}:${DB_PORT}/${DB_NAME}` |
| `PORT` | Service Port | `5000` |
| `POSTGREST_URL` | Postgrest url | `http://localhost:3000` |
| `PGOPTIONS` | PG Options | `-c search_path=storage,public` |
| `FILE_SIZE_LIMIT` | | `52428800` |
| `STORAGE_BACKEND` | Backend for storage | `file` |
| `FILE_STORAGE_BACKEND_PATH` | Storage backend path | `/bitnami/supabase-storage` |
| `TENANT_ID` | Tenant ID | `stub` |
| `REGION` | Region | `stub` |
| `GLOBAL_S3_BUCKET` | Global S3 Bucket | `stub` |
#### Read-only environment variables
| Name | Description | Value |
|-----------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------|
| `SUPABASE_STORAGE_BASE_DIR` | Supabase-storage installation directory. | `${BITNAMI_ROOT_DIR}/supabase-storage` |
| `SUPABASE_STORAGE_LOGS_DIR` | Directory where Supabase-storage logs are stored. | `${SUPABASE_STORAGE_BASE_DIR}/logs` |
| `SUPABASE_STORAGE_LOG_FILE` | Directory where Supabase-storage logs are stored. | `${SUPABASE_STORAGE_LOGS_DIR}/supabase-storage.log` |
| `SUPABASE_STORAGE_BIN_DIR` | Supabase-storage directory for binary executables. | `${SUPABASE_STORAGE_BASE_DIR}/node_modules/.bin` |
| `SUPABASE_STORAGE_TMP_DIR` | Directory where Supabase-storage temporary files are stored. | `${SUPABASE_STORAGE_BASE_DIR}/tmp` |
| `SUPABASE_STORAGE_PID_FILE` | Path to the PID file for Supabase-storage. | `${SUPABASE_STORAGE_TMP_DIR}/supabase-storage.pid` |
| `SUPABASE_STORAGE_EXTRA_ENV_FILE` | File to store extra environment variables for the supabase-storage service. | `${SUPABASE_STORAGE_BASE_DIR}/.env` |
| `SUPABASE_STORAGE_DAEMON_USER` | postgrest system user. | `supabase` |
| `SUPABASE_STORAGE_DAEMON_GROUP` | postgrest system group. | `supabase` |
### Running commands
To run commands inside this container you can use `docker run`, for example to execute `supabase-storage --help` you can follow the example below:
@@ -113,6 +127,12 @@ docker run --rm --name supabase-storage bitnami/supabase-storage:latest --help
Check the [official Supabase Storage documentation](https://github.com/supabase/storage-api) for more information about how to use Supabase Storage.
## Notable Changes
### Starting January 16, 2024
* The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.
## Contributing
We'd love for you to contribute to this Docker image. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution.