sr2/link-stack
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Secure digital helpdesk platform
352 commits 24 branches 47 tags 8.4 MiB
Find a file
Darren Clarke aaa2b059ff Merge branch 'add-microsoft-auth' into 'main' 
Add Azure auth

See merge request digiresilience/link/link-stack!17
2025-01-20 12:35:10 +00:00
apps Add Azure auth 2025-01-20 13:26:50 +01:00
docker Update signal-cli-rest-api Docker version 2024-10-07 06:39:44 +00:00
packages Cleanup dependencies 2024-09-27 13:11:31 +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 Hardcode rewrite destinations 2024-08-28 10:42:50 +02:00
.nvmrc Align node and npm versions to fix overrides 2023-06-07 10:25:53 +00:00
LICENSE.md Begin addon reorganization 2023-05-03 10:36:37 +00:00
package-lock.json Cleanup dependencies 2024-09-27 13:11:31 +02:00
package.json Update deps and Docker images 2024-09-27 11:22:45 +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