Skip to content

GESS Development VS Code Workspace

This setup opens the main GESS development repositories and installation project together in one VS Code multi-root workspace.

This allows GitHub Copilot to inspect related code across EMS, BESS simulator backend, BESS simulator frontend, and the SCADA/Docker installation project while keeping the repositories independent.

Local Folder Structure

/home/anura/
├── ES100CX12S/
├── bess_simulator/
│   └── EnergySyc_EMS_ES100Cx12S_BESS_simulator/
├── bess-simulator-frontend/
├── scada_EV_server_installation/
│   └── scada_installation_to_remote_server/
│       └── working/
│           └── docker_installation/
└── gess-ems-dev.code-workspace

1. Create the Workspace File

Create the workspace file in your home directory:

nano ~/gess-ems-dev.code-workspace

Paste:

{
  "folders": [
    {
      "name": "EMS",
      "path": "/home/anura/ES100CX12S"
    },
    {
      "name": "BESS Simulator Backend",
      "path": "/home/anura/bess_simulator/EnergySyc_EMS_ES100Cx12S_BESS_simulator"
    },
    {
      "name": "BESS Simulator Frontend",
      "path": "/home/anura/bess-simulator-frontend"
    },
    {
      "name": "SCADA Docker Installation",
      "path": "/home/anura/scada_EV_server_installation/scada_installation_to_remote_server/working/docker_installation"
    }
  ],
  "settings": {
    "git.autoRepositoryDetection": "subFolders",
    "search.useIgnoreFiles": true,
    "search.useGlobalIgnoreFiles": true
  }
}

Save in nano:

Ctrl+O
Enter
Ctrl+X

2. Start the Workspace

Run:

code ~/gess-ems-dev.code-workspace

VS Code will open:

EMS
BESS Simulator Backend
BESS Simulator Frontend
SCADA Docker Installation

GitHub Copilot can then use code from all of these workspace folders when troubleshooting or developing.

3. Repositories Stay Separate

The workspace does not combine Git repositories.

Each project keeps its own .git, branches, commits, remotes, and pull/push history.

Check any repository with:

git rev-parse --show-toplevel
git status

Examples:

cd ~/ES100CX12S
git status
cd ~/bess_simulator/EnergySyc_EMS_ES100Cx12S_BESS_simulator
git status
cd ~/bess-simulator-frontend
git status
cd ~/scada_EV_server_installation/scada_installation_to_remote_server/working/docker_installation
git status

4. Docker Deployment Remains Independent

Opening these projects in one VS Code workspace does not affect Docker deployment.

                     VS Code + Copilot
                            |
       +--------------------+---------------------+
       |                    |                     |
      EMS            BESS Simulator        BESS Simulator
     source              Backend               Frontend
       |                    |                     |
       +---------- Docker / deployment ---------+
                            |
                   SCADA Docker Installation

The EMS, simulator backend, simulator frontend, and installation code can still be built and deployed separately.

5. Useful Copilot Requests

Check the EMS PCS Modbus client against the BESS simulator backend
and identify why the PCS power command is failing.
Trace a simulator frontend command through the backend and compare it
with the EMS Modbus implementation.
Check whether changes made in EMS require any changes to the
docker installation configuration.
Compare the Docker Compose configuration with the EMS and BESS
simulator service names and network configuration.

Quick Start

Normally you only need:

code ~/gess-ems-dev.code-workspace

No symlinks are required. The VS Code multi-root workspace gives Copilot visibility into all related projects while keeping Git repositories and deployment containers independent.