2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00
2026-11-09 15:27:14 +01:00

claper

Claper: interactive presentations, polls, quizzes and Q&A for your audience, for Co-op Cloud

  • Maintainer: @ineiti
  • Category: Apps
  • Status: 0, work-in-progress
  • Image: ghcr.io/claperco/claper, 4, upstream
  • Healthcheck: Yes
  • Backups: Yes
  • Email: Yes (SMTP)
  • Tests: No
  • SSO: Yes (OIDC)

Quick start

  • abra app new claper --secrets
  • abra app config <app-name>
  • abra app deploy <app-name>
  • abra app cmd <app-name> app set_admin_password

On first start Claper creates the admin account admin@claper.co with the password claper. set_admin_password replaces it with the admin_pass secret printed by abra app new --secrets. Do this right after the first deploy, the default password is public.

Database migrations and seeds run on every start of the app container.

Email

Without SMTP, Claper uses its local mail adapter and drops all mails (account confirmation, password resets, magic links). To send mails:

COMPOSE_FILE="$COMPOSE_FILE:compose.smtp.yml"
SMTP_RELAY=smtp.example.com
SMTP_USERNAME=claper@example.com
SECRET_SMTP_PASS_VERSION=v1
  • abra app secret insert <app-name> smtp_pass v1 <password>
  • abra app deploy <app-name> --force

Single sign-on (OIDC)

Create a client at your provider (e.g. Authentik or Keycloak) with the redirect URI https://<DOMAIN>/users/oidc/callback, then:

COMPOSE_FILE="$COMPOSE_FILE:compose.oidc.yml"
OIDC_ISSUER=https://authentik.example.com/application/o/claper/
OIDC_CLIENT_ID=claper
SECRET_OIDC_SECRET_VERSION=v1
  • abra app secret insert <app-name> oidc_secret v1 <client-secret>
  • abra app deploy <app-name> --force

To allow only OIDC logins (DISABLE_PASSWORD_LOGIN=true), first log in once as admin@claper.co, log in once via OIDC with the account that should be the admin, promote it to admin in the admin panel, and only then enable the option.

S3 storage

Uploaded presentations are stored in the uploads volume by default. To use S3 (or an S3-compatible service) instead, enable compose.s3.yml in the config and insert the secret key with abra app secret insert <app-name> s3_secret v1 <secret-access-key>.

Backups

Both the uploads volume and a pg_dump of the database are backed up by backupbot.

S
Description
No description provided
Readme
46 KiB
Languages
Shell 52.9%
Elixir 47.1%