Documentation Backend

[frank-bee]

To be able to use digger productively as a large company as we are, we need a better documentation about the backend:

• how is the architecture?
• what kind of data is sent to the backend?
• is the connection secure ( auth z , auth n, encryption)?
• is there a way to setup the backend on-premise / in the own (AWS) cloud account? how?

[ZIJ]

Thanks so much for reporting @frank-bee ! Great and super helpful points, we need to improve docs

• architecture: basically we have a minimal orchestrator backend and a CLI wrapper on top of Terraform. Some more details here: https://diggerdev.notion.site/Why-digger-introduces-an-orchestrator-3d28029d53a3473d9c9e5f54f3b52d91
• data sent to backend: nothing sensitive, no secrets, not even Terraform code. That's all handled in the CI workers. Telemetry also anonymized: https://github.com/diggerhq/digger/blob/develop/pkg/usage/usage.go
• connection security: https with an API token, auth on Digger Cloud, provided by Frontegg; if you choose to self-host you can also integrate your own auth provider eg Auth0, Okta, etc
• setting up backend on-prem: yes, docs are severely lacking though atm. Will get back to you on this asap

[jseiser]

• setting up backend on-prem: yes, docs are severely lacking though atm. Will get back to you on this asap

Any update on this?

[chrisferry]

I'm attempting to set this up on-prem and running into a bunch of undocumented issues. Any movement on this?