release 0.53

Author: Pascal-Delange

api

@@ -1,9 +1,9 @@
 name: marble
 
 x-backend-image-version: &backend-image-version
-  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.52.1
+  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.53.2
 x-frontend-image-version: &frontend-image-version
-  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.52.0
+  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.53.0
 
 x-shared-environment: &shared-env
   ENV: development
@@ -23,6 +23,7 @@ x-backend-environment: &backend-env
   CASE_MANAGER_BUCKET_URL: ${CASE_MANAGER_BUCKET_URL:-}
 
   FIREBASE_AUTH_EMULATOR_HOST: firebase-auth:9099
+  FIREBASE_API_KEY: placeholder
 
   # default value of GOOGLE_CLOUD_PROJECT must be kept if working with the emulator (and the emulator is running in the docker image below)
   GOOGLE_CLOUD_PROJECT: test-project
@@ -42,12 +43,9 @@ x-frontend-environment: &frontend-env
   SESSION_SECRET: ${SESSION_SECRET:-}
   SESSION_MAX_AGE: 43200
 
-  MARBLE_API_URL_SERVER: http://api:8080
+  MARBLE_API_URL: http://api:8080
 
-  FIREBASE_AUTH_EMULATOR_HOST: localhost:9099
-  FIREBASE_API_KEY: placeholder
-  # default value of FIREBASE_PROJECT_ID must be kept if working with the emulator (and the emulator is running in the docker image below)
-  FIREBASE_PROJECT_ID: test-project
+  TEST_FIREBASE_AUTH_EMULATOR_HOST: localhost:9099
 
 services:
   db:

docker-compose-dev.yaml

@@ -1,19 +1,19 @@
 name: marble
 
 x-backend-image-version: &backend-image-version
-  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.52.1
+  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.53.2
 x-frontend-image-version: &frontend-image-version
-  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.52.0
+  image: europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.53.0
 
 x-shared-environment: &shared-env
   ENV: ${ENV}
-  MARBLE_APP_URL: ${MARBLE_APP_URL}
   SENTRY_DSN: ${SENTRY_DSN}
   DISABLE_SEGMENT: ${DISABLE_SEGMENT:-false}
 x-backend-environment: &backend-env
   LICENSE_KEY: ${LICENSE_KEY}
 
   PORT: ${API_PORT:-8080}
+  MARBLE_APP_URL: ${MARBLE_APP_URL}
 
   PG_HOSTNAME: ${PG_HOSTNAME}
   PG_PORT: ${PG_PORT}
@@ -30,6 +30,9 @@ x-backend-environment: &backend-env
   GOOGLE_CLOUD_PROJECT: ${GOOGLE_CLOUD_PROJECT}
   GOOGLE_APPLICATION_CREDENTIALS: ${GOOGLE_APPLICATION_CREDENTIALS}
 
+  FIREBASE_API_KEY: ${FIREBASE_API_KEY}
+  FIREBASE_PROJECT_ID: ${FIREBASE_PROJECT_ID}
+
   REQUEST_LOGGING_LEVEL: ${REQUEST_LOGGING_LEVEL}
   LOGGING_FORMAT: ${LOGGING_FORMAT}
 
@@ -64,7 +67,7 @@ x-frontend-environment: &frontend-env
   SESSION_SECRET: ${SESSION_SECRET}
   SESSION_MAX_AGE: ${SESSION_MAX_AGE}
 
-  MARBLE_API_URL_SERVER: ${MARBLE_API_URL_SERVER}
+  MARBLE_API_URL: ${MARBLE_API_URL}
 
 services:
   # NB: the docker compose file includes a postgres image for the sake of completeness, but we strongly

docker-compose.yaml

@@ -15,7 +15,8 @@ The `OFFLOADING_JOB_INTERVAL`, `OFFLOADING_BEFORE`, `OFFLOADING_BATCH_SIZE`, `OF
 
 ### Storage classes
 
-Old decisions are likely to be rarely consulted. For further cost savings, we recommend you configure your blob storage bucket to automatically move the data to long-term storage classes using lifecycle rules. Objects are stored by decision status prefix (`offloading/decision_rules/{status}` where `status` is one of `error`, `hit`, `no_hit`), so it is possible in most blob storage solutions to configure different lifecycle rules for rules that did or did not result in a hit.
+The objects thus stored have a small size, even if they are cumbersome to store in a relational database. We strongly suggest that you write the objects to the "standard" object class, and do not use any lifecycle rules other than (optionally) deleting objects after a given time. Deleting the objects under `{bucket}/offloading/decision_rules` will not cause any errors in the application.
 
-Data offloaded to Google Cloud Storage may further use the custom time metadata attribute instead of the object's creation time for lifecycle rules.
-As an example, Marble's managed environment moves objects to "Nearline" storage class after a month, "Coldline" after 3 months and "Archive" after a year.
+Specifically, moving objects to "archive" type storage classes is dangerous because the per-operation cost greatly exceeds the storage cost.
+
+Objects are stored by decision status prefix (`offloading/decision_rules/{status}` where `status` is one of `error`, `hit`, `no_hit`), so it is possible in most blob storage solutions to configure different lifecycle rules for rules that did or did not result in a hit.

front

@@ -1,2 +1,2 @@
-MARBLE-FRONT-VERSION=0.52.0
-MARBLE-BACK-VERSION=0.52.1
+MARBLE-FRONT-VERSION=0.53.0
+MARBLE-BACK-VERSION=0.53.2