Review your generated config

Inspect the generated config.json and focus only on the keys that matter for a first rollout.

Your distribution config lives here:

.divekit/distributions/M0/config.json

This file was already created by divekit init.

For the beginner workflow, focus on these keys:

• version
• remote
• groupId
• members.permissions

Open the file

Open .divekit/distributions/M0/config.json in your editor.

The exact values depend on what you entered during divekit init, but a typical result looks roughly like this:

{
  "version": "2.0",
  "remote": "gitnrw",
  "groupId": 311,
  "members": {
    "permissions": "reporter"
  }
}

Read only these keys

version

This is the stored config format version.
For beginners, the important point is just that Divekit created it for you.

remote

This must match the host you configured earlier with divekit auth.

groupId

This is the main target group ID on the GitLab instance.

members.permissions

This defines the default permission level for members that will be attached during distribution.

Once you provide members later in the course, a members.path entry appears here as well. Its value looks like $DIVEKIT_MEMBERS/2026-07-16_10-24-55_M0_members.json and points to the stored member input in your user-level Divekit directory.

What not to do here

This lesson is not about rebuilding the file by hand.

At beginner level, avoid these habits:

• copying a full config template from documentation without checking what init already created
• adding advanced config fields you do not need yet
• trying to solve member handling by hand-editing file paths too early

Check

Open .divekit/distributions/M0/config.json again and answer: