Provisioning via SSH
This section describes the SSH-based provisioning workflow.
The SSH approach provides direct access to the controller and its configuration. All changes are made by writing files to the persistency directory, allowing full control over configuration behavior.
This method is well-suited for:
- quick provisioning setup without additional tooling
- workflows that combine configuration and firmware updates
Because changes are applied directly, this approach offers no safeguards against misconfiguration and requires careful handling.
1. Audience and assumptions
We assume the following:
- you are a mid- or senior-level software engineer with linux command line knowledge
- you are working on Windows 11
- you are using PowerShell
- SSH access to the controller is already available
The SSH-based provisioning method will work on other host operating systems and with other terminal applications as well, but the instructions in this documentation are tailored to the above assumptions for simplicity. Minor adjustments may be needed.
2. Background information
- All non-default configuration is stored in the persistency directory. For a detailed explanation of configuration storage, file structure, and applying changes, see the Configuration Storage reference.
- To understand master-slave scoping, see the Master-Slave Configuration reference.
- For parameter mapping, see the OCPP parameter table.
3. Getting started
For getting started with SSH-based provisioning, the following resources are available:
For guided walkthroughs, see Provisioning via SSH Tutorial. Here, you'll be guided through a selection of common tasks from start to finish, with background information and explanations along the way.
For task-based commands and reusable procedures, see Provisioning via SSH Cookbook. This is a collection of common provisioning tasks, providing a reference for quick lookup and execution.