Mekari · Deployment Helper · Install guide

CIMB SMART
Versioning Helper

Chrome extension floating panel on Officeless Studio (studio.* / studio-* hosts) for Visual Programming, Experience Manager (UI — Single / UI — Multiple), and Data Manager. Sign in once with Google, then sync to git, push line cherry-picks to Officeless Source, and promote to Target — all from the plugin. No localhost setup required.

Download ZIP · Load unpacked API deployment-helper.smart-cimb.com Auth Sign in with Google Version …

Download extension (.zip) Install steps ↓ Use the panel ↓ Loading build info…

1. Download & install (step by step)

Chrome cannot install a ZIP directly. Unzip it, then load the folder as an unpacked extension. Current release: v1.3.18 (also shown in the chip above when build info loads).

Download the ZIP
Click officeless-deployment-helper-extension.zip (also available at the top of this page), or open deployment-helper.smart-cimb.com and download from there.
Unzip the archive
You should get a folder named officeless-deployment-helper-extension that contains manifest.json, background.js, icons/, etc.
```
unzip officeless-deployment-helper-extension.zip
# → officeless-deployment-helper-extension/
```
Open Chrome extensions
Go to chrome://extensions in the address bar.
Enable Developer mode
Toggle Developer mode in the top-right corner.
Load unpacked
Click Load unpacked and select the unzipped officeless-deployment-helper-extension folder (the one that contains manifest.json — not the parent Downloads folder).
Confirm it appears
You should see CIMB SMART Versioning Helper in the extensions list. Pin it from the puzzle-piece menu if you want the popup handy.
Open Officeless Studio
Navigate to a supported editor (Visual Programming, Experience Manager, or Data Manager). The floating CIMB SMART Versioning Helper panel appears when kind + id are detected.

You do not need to clone the repo or run npm run dev on localhost. The extension talks to production Helper at https://deployment-helper.smart-cimb.com.

After updating the ZIP, return to chrome://extensions and click the reload icon on the extension card (or Remove + Load unpacked again).

2. Sign in & use the panel

Everything runs from the plugin. You do not need to open the Deployment Helper website for day-to-day sync / push / promote. (The website may later sit behind VPN; the extension stays usable without VPN.)

First-time sign in

On first install (or after logout), the panel shows Sign in with Google. Use a Mekari account (@mekari.com or @aux.mekari.com).

Panel signed out — Sign in with Google — Signed out — click **Sign in with Google**.

Google account chooser for Officeless DevOps Central — Google popup — choose your Mekari account to continue to Officeless DevOps Central.

After login — simple menu

The panel shows the detected asset (kind + id) and three actions. Use the gear at the bottom for Target gateway settings, and logout to clear the Helper session.

Signed-in panel with three actions — Signed in — Sync / Push / Promote. Promote stays grey until Target is configured.

Target gateway settings panel — Gear icon — set Target gateway URL, username, and password, then **Save Target settings** (optional **Test connection**).

Typical flow

Sync a Copy to Git Repo Branch — pull the live Officeless Source asset into the git repo under feature/<your-name> (commit + push on the server).
Edit on your feature branch (or in Studio), then return to the same editor page.
Push from Repo Branch to Officeless — opens a side-by-side line cherry-pick modal. Tick the lines you want, then Apply selected or Update all. The user who pushes is recorded automatically (audit / PIC).
Promote to Target — same cherry-pick UX, but Source → Target. Enable it by filling Target in the gear settings first.

Panel after opening push review — After Sync, use **Push from Repo Branch to Officeless** to review line changes.

Line cherry-pick (merging resolution)

Changed lines are selectable. Unchanged blocks are omitted so you can focus on the diff. Owners are shown for Source vs downloaded copy. Script / JSON fields are compared line-by-line.

VP push line cherry-pick modal — Visual Programming — select lines, then Apply selected / Update all.

Experience Manager SEM push line cherry-pick — Experience Manager (UI — Single) — same cherry-pick UI; pusher is recorded.

Sync a Copy to Git Repo Branch

Fetches the asset from Officeless Source, writes it under officeless-assets/, commits on feature/<you>, and pushes to GitHub.

Push from Repo Branch to Officeless

Diffs your branch copy vs live Source, lets you cherry-pick lines (including JS), deploys the merge to Source, and records who pushed.

Promote to Target

Same cherry-pick flow toward the Target gateway. Greyed out until Target URL / username / password are saved in settings.

Hide / restore

Minimize with _ in the header; restore via the CSVH chip. Double-click the status badge to expand/collapse. Logout clears the Helper session cookie.

3. Architecture

Studio page → extension panel → production Helper API → git feature branch & Officeless gateways. No local Deployment Helper process is required.

flowchart LR
  Studio["Officeless Studio editor"] --> Panel["CIMB SMART Versioning Helper"]
  Panel --> API["deployment-helper.smart-cimb.com /api/extension"]
  API --> Git["GitHub feature/<user> + officeless-assets"]
  API --> Source["Officeless Source gateway"]
  API --> Target["Target gateway optional"]

4. What each action does

Action	API	Result
Sync a Copy to Git Repo Branch	`POST /api/extension/download-commit`	Asset JSON on `feature/<you>` + commit / push
Push from Repo Branch to Officeless	`diff-sync` → `apply-sync`	Line cherry-pick merge deployed to Source; pusher recorded
Promote to Target	`diff-promote` → `apply-promote`	Line cherry-pick merge deployed to Target (after Target settings)
Test / Save Target	`gateway-target` · `gateway-target/test`	Stores Target credentials in the Helper session; enables Promote

5. Troubleshooting

Panel says “Not on a supported editor” / Detecting asset… — open Visual Programming, Experience Manager, or Data Manager and wait until the meta line shows an id (URL, badge + id in the header, or network hints).
Signed out / Sign in required — click Sign in with Google and pick a Mekari account. Allow popups if the Google window is blocked.
Promote is greyed out — open the gear icon, fill Target gateway URL / username / password, then Save Target settings (use Test connection to verify).
Push failed: non-fast-forward — retry Sync / Push; Helper rebases onto the latest feature/<you> before pushing.
Load unpacked fails — select the inner folder that contains manifest.json, not the ZIP file itself.
After downloading a new ZIP — reload the extension on chrome://extensions so you pick up the latest version (e.g. v1.3.18).