Postgres Upgrades and changes

.circleci/config.yml

@@ -24,7 +24,9 @@ jobs:
 
       - run:
           name: "Setup: Copy environment variables"
-          command: cp .env_circleci .env
+          command: |
+            cp .env_circleci .env
+            cp my-postgres_sample.conf my-postgres.conf
 
       - run:
           name: "Setup: Create directories for MinIO (cannot be made by docker for some reason)"

.gitignore

@@ -40,3 +40,5 @@ caddy_config/
 caddy_data/
 
 home_page_counters.json
+my-postgres.conf
+tests/config/state.json

docker-compose.yml

@@ -78,8 +78,8 @@ services:
       /bin/sh -c "
       set -x;
       if [ -n \"$MINIO_ACCESS_KEY\" ] && [ -n \"$MINIO_SECRET_KEY\" ] && [ -n \"$MINIO_PORT\" ]; then
-        until /usr/bin/mc alias set minio_docker http://minio:$MINIO_PORT $MINIO_ACCESS_KEY $MINIO_SECRET_KEY && break; do 
-          echo '...waiting...' && sleep 5; 
+        until /usr/bin/mc alias set minio_docker http://minio:$MINIO_PORT $MINIO_ACCESS_KEY $MINIO_SECRET_KEY && break; do
+          echo '...waiting...' && sleep 5;
         done;
         /usr/bin/mc mb minio_docker/$AWS_STORAGE_BUCKET_NAME || echo 'Bucket $AWS_STORAGE_BUCKET_NAME already exists.';
         /usr/bin/mc mb minio_docker/$AWS_STORAGE_PRIVATE_BUCKET_NAME || echo 'Bucket $AWS_STORAGE_PRIVATE_BUCKET_NAME already exists.';
@@ -110,17 +110,18 @@ services:
   #   Database Service
   #-----------------------------------------------
   db:
-    image: postgres:12-alpine
+    image: postgres:18-alpine
     env_file: .env
     environment:
-      - PGDATA=/var/lib/postgresql/data/pgdata
+      - PGDATA=/var/lib/postgresql/18/docker
       - POSTGRES_PASSWORD=${DB_PASSWORD}
-    command: ["postgres", "-c", "log_statement=all", "-c", "log_destination=stderr"]
+    command: ["postgres", "-c", "log_statement=all", "-c", "log_destination=stderr", "-c", "config_file=/etc/postgresql/postgresql.conf"]
     ports:
       - 5432:5432
     volumes:
-      - ./var/postgres:/var/lib/postgresql/data:delegated
+      - ./var/postgres:/var/lib/postgresql/18/:delegated
       - ./backups:/app/backups
+      - ./my-postgres.conf:/etc/postgresql/postgresql.conf
     restart: unless-stopped
     logging:
       options:

documentation/docs/Developers_and_Administrators/Codabench-Installation.md

@@ -21,9 +21,10 @@ On a fresh installation, you will need to use the following command to get your
 ```bash
 cd codabench
 cp .env_sample .env
+cp my-postgres_sample.conf my-postgres.conf
 ```
 
-Then edit the necessary settings inside. The most important are the database, storage, and Caddy/SSL settings. For a quick **local** setup, you should not need to edit this file. For a [public server deployment](How-to-deploy-Codabench-on-your-server.md), you will have to modify some settings.
+Then edit the necessary settings inside. The most important are the database, storage, and Caddy/SSL settings in the `.env`. For a quick **local** setup, you should not need to edit these files. For a [public server deployment](How-to-deploy-Codabench-on-your-server.md), you will have to modify some settings.
 
 !!! warning "It is important to change the default passwords if you intend for the instance to be public"
 

documentation/docs/Developers_and_Administrators/How-to-deploy-Codabench-on-your-server.md

@@ -21,10 +21,11 @@ Then you need to modify the `.env` file with the relevant settings. This step is
 - Go to the folder where codabench is located (`cd codabench`)
 ```bash
 cp .env_sample .env
+cp my-postgres_sample.conf my-postgres.conf
 ```
 
 
-Then edit the variables inside the `.env` file.
+Then edit the variables inside the `.env` and the `my-postgres.conf` files. You can keep the default values of `my-postgres.conf` if you don't want to change anything
 
 ### Submissions endpoint
 For an online deployment, you'll need to fill in the IP address or domain name in some environment variables.