Files 📂

Upon installation, denget creates two JSON-formatted files used to store data and configuration.

data.json

This file can be found in denget\data. It’s used to store information about installed apps and for buckets sources.

It consists of two lists - installed and sources. Each item in installed consists of name, version, bucket, portable, path and executable fields, and items in sources of name and url fields.

Example of file contents:

{
    "installed": [
      {
        "name": "app1",
        "version": "1.0.0",
        "bucket": "main",
        "portable": true,
        "path": "C:\\Users\\admin\\denget\\apps",
        "executable": "C:\\Users\\admin\\denget\\apps\\app1\\1.0.0\\app1.exe"
      },
      {
        "name": "app2",
        "version": "1.19.1",
        "bucket": "cool",
        "portable": false,
        "path": "C:\\Program Files\\app2",
        "executable": "C:\\Program Files\\app2\\bin\\x64\\app2.exe"
      }
    ],
    "sources": [
      {
        "name": "main",
        "url": "<https://github.com/DenisionSoft/dgmain>"
      }
    ]
  }

rclone.conf

If you have rclone installed, this file contains configured remotes. Viewing and editing this file can be useful for cloud sources. Please, see Cloud support ☁️ for detailed information.

Configuration 📝

To view and edit denget files you can use a build-in command.

denget config

Gives you a list of data and configuration files used by denget which you can view and edit. File rclone.conf will be available if rclone is installed via denget so it’s easy to access. After picking a file, denget will try to detect available editors and prompt you to pick one, or press Enter to choose a default editor (in some cases that would invoke “Open with…” system dialog).

While it can be useful for troubleshooting or for advanced users, be careful when editing config files manually, as it may break denget functionality or cause unexpected behavior.

To see commands for managing denget installation, go to Managing denget installation 🛠️.