sr2/link-stack
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Secure digital helpdesk platform
398 commits 24 branches 47 tags 8.4 MiB
Find a file
Darren Clarke 5b89bfce7c Update group name
2025-08-20 10:20:36 +02:00
apps Update group name 2025-08-20 10:20:36 +02:00
docker Fix incoming Signal messages when conversation initiated from Zammad 2025-07-25 22:39:07 +02:00
packages Fix incoming Signal messages when conversation initiated from Zammad 2025-07-25 22:39:07 +02:00
.dockerignore metamigo-frontend: build and run in docker 2023-06-06 07:10:28 +00:00
.editorconfig Align node and npm versions to fix overrides 2023-06-07 10:25:53 +00:00
.gitignore Update Dockerfiles, add signal api generated outputs 2024-06-05 10:06:41 +02:00
.gitlab-ci.yml Remove base-url-changes from CI 2025-02-13 08:48:05 +01:00
.nvmrc Align node and npm versions to fix overrides 2023-06-07 10:25:53 +00:00
docker-compose.bridge-dev.yml Group refinements 2025-07-02 12:07:12 +02:00
LICENSE.md Begin addon reorganization 2023-05-03 10:36:37 +00:00
package-lock.json Add Signal auto-group creation 2025-06-10 14:02:21 +02:00
package.json Group refinements 2025-07-02 12:07:12 +02:00
README.md Update readme 2 2024-10-07 15:49:29 +02:00
turbo.json Update deps 2024-06-12 08:27:30 +02:00

README.md

CDR Link

CDR Link is a simple & streamlined helpdesk that lets you tag, assign and respond to your tickets. It is developed by the Center for Digital Resilience and powered by Zammad.

Key differences between CDR Link and a standard Zammad installation:

  • In addition to the full Zammad interface, CDR Link also provides a simplified 'shell' interface that focuses on the most-commonly-used functionality.
  • Additional channels to communicate with users, including Signal, Whatsapp & Twilio voice messaging.
  • More stringent privacy defaults: ticket data is never sent over email and calls to third-party services are restricted.

Developing

This is a monorepo that contains CDR Link and several supporting applications and libraries. It also includes Dockerfiles to build all of the other containers required for an installation. By tagging our own versions of these dependencies, we can make sure that different versions of the supporting containers all work together and are updated in sync.

We use Turborepo to manage development and building of the packages. To get started:

  • npm install in the root directory
  • turbo build to build all packages

To run a single package:

  • turbo dev --filter @link-stack/link