codalab · Didayolo · Sep 18, 2026 · Sep 1, 2026 · Sep 1, 2026 · Aug 3, 2026
diff --git a/.env_sample b/.env_sample
@@ -88,6 +88,13 @@ ENABLE_SIGN_UP=True
 ENABLE_SIGN_IN=True
 
 
+# -----------------------------------------------------------------------------
+# Enable or disable the External Competitions feature (button, page, API,
+# and the daily fetch task). Off by default - intended for the main instance only.
+# -----------------------------------------------------------------------------
+EXTERNAL_COMPETITIONS_ENABLED=False
+
+
 # # S3 storage example
 # STORAGE_TYPE=s3
 # AWS_ACCESS_KEY_ID=12312312312312312331223

diff --git a/compute_worker/compute_worker.py b/compute_worker/compute_worker.py
diff --git a/compute_worker/uv.lock b/compute_worker/uv.lock
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -56,7 +56,7 @@ services:
   # Minio local storage helper
   #----------------------------------------------------------------------------------------------------
   minio:
-    image: minio/minio:RELEASE.2025-04-22T22-12-26Z
+    image: quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z
     command: server /export
     volumes:
       - ./var/minio:/export
@@ -69,7 +69,7 @@ services:
       interval: 5s
       retries: 5
   createbuckets:
-    image: minio/mc:RELEASE.2025-07-21T05-28-08Z
+    image: quay.io/minio/mc:RELEASE.2025-07-21T05-28-08Z
     depends_on:
       minio:
         condition: service_healthy
@@ -219,9 +219,7 @@ services:
     deploy:
       resources:
         limits:
-          # Limit memory substantially here so we see any problems that may
-          # appear on Heroku ahead of time
-          memory: 256M
+          memory: 15GB
 
   compute_worker:
     command: ["celery -A compute_worker worker -l info -Q compute-worker -n compute-worker@%n"]
@@ -244,7 +242,7 @@ services:
     environment:
       - BROKER_URL=pyamqp://${RABBITMQ_DEFAULT_USER}:${RABBITMQ_DEFAULT_PASS}@${RABBITMQ_HOST}:${RABBITMQ_PORT}//
       # Make the worker leave behind the submission so we can examine it
-      - CODALAB_IGNORE_CLEANUP_STEP=1
+      - COMPUTE_WORKER_NO_CLEANUP=True
     tty: true
     logging:
       options:

diff --git a/documentation/docs/Developers_and_Administrators/External-Competitions.md b/documentation/docs/Developers_and_Administrators/External-Competitions.md
@@ -0,0 +1,63 @@
+External Competitions lets a Codabench instance show a browsable list of public competitions hosted on *other* Codabench and CodaLab instances, fetched and synced automatically once a day. It's off by default and intended for the main `codabench.org` instance rather than self-hosted deployments.
+
+## For Codabench administrators
+
+### Enabling the feature
+
+Set the following in your `.env` file:
+
+```
+EXTERNAL_COMPETITIONS_ENABLED=True
+```
+
+This turns on the External Competitions page, a banner/link to it on the public benchmarks and competitions page, the two read-only API endpoints, and the daily Celery beat task that fetches and syncs competitions. Leaving it `False` (the default) disables all of it - the API endpoints return a 404, and the page and the banner linking to it aren't shown.
+
+### Adding a platform to sync from
+
+Platforms are managed from the Django admin, under **External Competitions -> External platforms -> Add**. Each platform needs:
+
+| Field | Description |
+|---|---|
+| Name | Display name shown on the competition tiles (e.g. "Codabench @ LISN") |
+| Platform type | `Codabench instance` or `CodaLab instance` |
+| Competitions fetch URL | The API endpoint to get that platform's list of public competitions |
+| Competition base URL | The base URL used to create complete link for each competition |
+| Active | Unchecking this skips the platform in the daily fetch (already-synced competitions stay visible - see note below) |
+
+Once saved, the platform is picked up by the next scheduled fetch (or trigger one manually, see below).
+
+### How the sync works
+
+`fetch_external_competitions` (`src/apps/external_competitions/tasks.py`) runs once a day via Celery beat. For each active platform it calls the fetcher matching its platform type (`codabench_fetcher.py` or `codalab_fetcher.py`) and then diffs the result against what's already stored:
+
+- Competitions present in the fetch are created or updated (matched by `competition_url`).
+- Competitions no longer present in the fetch are deleted.
+
+Each run writes an `ExternalFetchLog` entry (visible in the admin) recording the outcome (`SUCCESS`/`FAILURE`), counts (`new_count`/`updated_count`/`deleted_count`), and, on failure, an error message - check there first if a platform's competitions look stale or missing.
+
+!!! note
+    Deactivating a platform (`is_active=False`) only stops it from being fetched going forward - competitions already synced from it stay visible on the public list until manually removed.
+
+To trigger a fetch immediately instead of waiting for the daily schedule:
+
+```bash
+docker compose exec django ./manage.py shell -c "from external_competitions.tasks import fetch_external_competitions; fetch_external_competitions()"
+```
+
+## For platform administrators
+
+If you run your own Codabench or CodaLab instance and would like your public competitions to be discoverable on `codabench.org`'s External Competitions page, you can request to be added.
+
+### Registering your platform
+
+Send an email to **info@codabench.org** with the subject **"Platform Registration for External Competitions"**, including:
+
+- **Your platform's name and type** (Codabench, CodaLab instance, or other).
+- **Your competitions fetch URL** - the API endpoint we'll use once a day to retrieve your list of public competitions (for example, a Codabench instance's `.../api/competitions/public/`). This endpoint must be publicly reachable without authentication, since the fetch runs unattended.
+- **Your competition base URL** - the base URL used to build the link back to each competition on your site, so visitors clicking a competition on `codabench.org` land on the right page on yours.
+
+Please share as much detail as you can, **especially about the fetch URL** - pagination behavior, response format, expected size of the response, rate limits, or anything else likely to affect an automated daily fetch. The more we know upfront, the more reliably we can keep your competitions in sync.
+
+### Unregistering your platform
+
+To have your platform's competitions removed or paused, email **info@codabench.org** asking us to deactivate (or delete) fetching for your platform, including your platform's name and/or URL so we can identify it.
diff --git a/...on/docs/Developers_and_Administrators/How-to-deploy-Codabench-on-your-server.md b/...on/docs/Developers_and_Administrators/How-to-deploy-Codabench-on-your-server.md
@@ -243,6 +243,8 @@ You can update these by:
 1. Replacing the logos in `src/static/img/` folder
 2. Updating the code in `src/templates/pages/home.html` to point to the right websites of your organizations
 
+!!! tip
+    Now that your instance is up and running, consider registering it with `codabench.org` as an [External Competitions](External-Competitions.md) platform. Once registered, your instance's public competitions are also listed on `codabench.org`'s own External Competitions page, giving them more visibility. See the [registration instructions](External-Competitions.md#registering-your-platform) for details.
 
 ## Frequently asked questions (FAQs)
 
@@ -374,7 +376,7 @@ MINIO_PORT=9000
   # Minio local storage helper
   #-----------------------------------------------
   minio:
-    image: minio/minio:RELEASE.2020-10-03T02-19-42Z
+    image: quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z
     command: server /export --certs-dir /root/.minio/certs
     volumes:
       - ./var/minio:/export
@@ -388,7 +390,7 @@ MINIO_PORT=9000
       interval: 5s
       retries: 5
   createbuckets:
-    image: minio/mc
+    image: quay.io/minio/mc:RELEASE.2025-07-21T05-28-08Z
     depends_on:
       minio:
         condition: service_healthy