DevLake Deployment & Configuration FAQs

Question 1

What permissions does the GitHub PAT need?

Accepted Answer

For full functionality including Copilot metrics, the PAT requires 'repo', 'read:org', 'read:user', 'copilot', and 'manage_billing:copilot' scopes.

Question 2

Can I deploy DevLake to AWS or GCP using this skill?

Accepted Answer

Currently, this skill supports local Docker and Azure deployments; support for AWS and GCP is planned for future updates.

Question 3

Do I need to have DevLake already running to use this skill?

Accepted Answer

No, the skill can handle initial deployment from scratch (Phase 1) or simply configure an existing instance that is already running (Phases 2 and 3).

Question 4

How does the skill handle my GitHub Personal Access Token (PAT)?

Accepted Answer

The skill uses a secure .devlake.env workflow, creating a temporary file for you to paste your token, which is then deleted automatically after the connection is established to ensure tokens are never saved in chat history.

Question 5

What are DORA metrics?

Accepted Answer

DORA metrics (Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service) are industry standards for measuring software delivery performance, all of which DevLake helps track.

DevLake Deployment & Configuration

Key Features

Use Cases

DevLake Deployment & Configuration

Key Features

Use Cases