JitNode Directory

JitNode uses a clear directory structure to organize executable programs and runtime data. Developers should have a basic understanding of JitNode's directory structure for better subsequent development, management, and debugging work.

In the desktop edition, the JitNode directory is located in the installation directory:

Path in MacOS

/Applications/Jit.app/Contents/Resources/app.asar.unpacked/JitNode

Path in Windows

C:\Program Files\jit\resources\app.asar.unpacked\JitNode

In the server edition, the JitNode directory is located in the Docker container:

Path in Docker Container

/data/JitNode

Typically, when deploying containers, the JitNode directory is mounted to the host machine, and developers can also find the JitNode directory in the corresponding directory on the host machine

Directory Overview

Overview

JitNode/
├── runJitNode.cmd/command    # desktop edition one-click startup script
├── home/                     # Runtime data directory
│   ├── version.json          # Version information
│   ├── node.json             # Configuration file
│   ├── environs/             # Runtime environments
│   └── logs/                 # Runtime logs
└── system/                   # Executable program directory

home/ Directory

home/ - Runtime Data

In the desktop edition, users can customize the path when running for the first time.

📋 ./ - Configuration Files

home/
├── version.json              # Installation package and dependency version information
├── node.json                 # JitNode node configuration file

🌍 environs/ - Runtime Environments

home/environs/
├── JED_xxx1.json            # Node default runtime environment configuration
├── JED_xxx1/                # Application directory for node default runtime environment
│   └── xxxOrg1/             # Development organization ID
│       └── xxxApp/          # Application ID
│           └── 1_0_0/       # Application version number
│               ├── [Source Code]   # Application source code (source code available in development mode)
│               ├── appData/ # Application data
│               └── dist/    # Build artifacts
└── ...

Environment Organization Structure

Adopts a four-level directory structure: Runtime Environment → Development Organization → Application → Version

📝 logs/ - Runtime Logs

home/logs/
├── upgrade.log             # Automatic update logs
├── server.log              # Service runtime logs
└── ...                     # Other log files

Docker-Specific Directories

The following directories only exist in Docker containers:

🗄️ databases/ - Built-in Database Files

home/databases/
├── redis/
│   ├── redis.config         # Redis configuration file
│   ├── redis.db            # Redis data file
│   └── redis.log           # Redis log file
└── mysql/
    ├── mysql.config        # MySQL configuration file
    ├── mysql.db           # MySQL data file
    └── mysql.log          # MySQL log file

system/ Directory

system/ - Executable Programs

🔧 bin/ - Third-party Programs

system/bin/
├── node/                   # Node.js
├── python/                 # Python
└── ...                     # Other dependency programs

📚 pyLibraris/ - Python Dependency Libraries for Each Application

system/pyLibraris/
└── [Organized by Runtime Environment/Development Organization/Application/Version]
    └── Python dependency libraries for each application version

Dependency Isolation

Each application version has independent Python dependency libraries, avoiding version conflicts.

🐛 Debugging Tools (Desktop Editon Only)

system/
└── jitDebuger.py           # Full code debugging entry point

Debugging Features

The desktop edition provides complete code debugging functionality, supporting breakpoints, variable monitoring, etc. For detailed usage methods, refer to Local Development and Debugging.

Quick Navigation

• Deploy Applications: Place applications in the home/environs/[Environment ID]/[Organization ID]/[Application ID]/[Version]/ directory
• View Logs: Check runtime logs in the home/logs/ directory
• Debug Code: Desktop edition uses system/jitDebuger.py for debugging. For detailed usage methods, refer to Local Development and Debugging.
• Configuration Modification: Edit home/node.json to modify JitNode configuration