v2.1.0

Important

Temporal container changes

It's been reported that the sqlite version of the Temporal container that was previously shipped with Ganymede caused issues, see #339 and #353 for more information. To fix this, I'm now recommending everyone to switch to the more "production-like" temporal setup, which uses a database. To perform this change, follow the below.

No workflow data will be saved from the previous container, so ensure that nothing is actively being archived

1. Bring down Ganymede docker compose down
2. Perform the following change to your docker-compose.yml file. The new Temporal container requires access to your database, make sure to update the POSTGRES_USER and POSTGRES_PWD with the username and password of your ganymede-db container.

-  ganymede-temporal:
-    container_name: ganymede-temporal
-    image: ghcr.io/zibbp/ganymede-temporal:latest
-    restart: unless-stopped
-    volumes:
-      - ./temporal:/data
-    ports:
-      - 7233:7233
-      - 8233:8233 # web ui - optional
+  ganymede-temporal:
+    image: temporalio/auto-setup:1
+    container_name: ganymede-temporal
+    depends_on:
+      - ganymede-db
+    environment:
+      - DB=postgresql # this tells temporal to use postgres (not the db name)
+      - DB_PORT=5432
+      - POSTGRES_USER=ganymede
+      - POSTGRES_PWD=PASSWORD
+      - POSTGRES_SEEDS=ganymede-db # name of the db service
+    ports:
+      - 7233:7233

3. Optionally add the web-ui service if you wish to use that.

+  ganymede-temporal-ui:
+    image: temporalio/ui:latest
+    container_name: ganymede-temporal-ui
+    depends_on:
+      - ganymede-temporal
+    environment:
+      - TEMPORAL_ADDRESS=ganymede-temporal:7233
+    ports:
+      - 8233:8080

4. Delete the temporal directory
5. Bring everything back up docker compose up -d
6. Ensure the temporal container is working fine docker logs ganymede-temporal and check that the API container is able to connect docker logs ganymede-api

Refer to the docker-compose.yml file for a full example.

What's Changed

If you've been running the :main image for either the API or frontend, now is a good time to switch back to the :latest tag.

Frontend

• Bump package versions
• Place theater mode button next to full screen button
• Show thumbnail when video hasn't begun playing yet
• Add sharp and ensure /app directory is writable
• Fix bug the prevented the VOD title component from coming back after exiting theater mode

API

• Use debian as the x86 docker base image
• Re-run live thumbnail download 10 minutes after the archive starts

Lots of bug fixes and package version bumps:

• feat(workflow): update live stream archives with correct vod ids by @Zibbp in #351
• Fixes 354 by @Zibbp in #357
• Fixes 2024 02 04 by @Zibbp in #361
• fix(exec): check if livechatworkflowid is populated by @Zibbp in #364
• fix: add comments by @Zibbp in #365
• feat(workflow): re-download live thumbnail again after 10 minutes by @Zibbp in #372
• build(deps): bump golangci/golangci-lint-action from 3.7.0 to 4.0.0 by @dependabot in #368
• build(deps): bump golang.org/x/crypto from 0.17.0 to 0.19.0 by @dependabot in #367
• build(deps): bump docker/metadata-action from 5.0.0 to 5.5.1 by @dependabot in #363
• build(deps): bump github.com/mattn/go-sqlite3 from 1.14.17 to 1.14.22 by @dependabot in #362
• build(deps): bump github.com/prometheus/client_golang from 1.17.0 to 1.18.0 by @dependabot in #338
• build(deps): bump github.com/labstack/echo/v4 from 4.11.3 to 4.11.4 by @dependabot in #332
• build(deps): bump golang.org/x/oauth2 from 0.15.0 to 0.17.0 by @dependabot in #366
• build(deps): bump actions/setup-go from 4 to 5 by @dependabot in #322
• build(deps): bump github/codeql-action from 2 to 3 by @dependabot in #326
• build(docker): use debian as base image by @Zibbp in #373

Full Changelog: v2.0.2...v2.1.0