esign_css Customization Branches & Dev/Test Method

Scope

Durable reference for the esign_css customization branch fleet (as of 2026-05) and the standard method for running/testing esign_css in a dev environment. The general FaceKom customization-branch index customization-branches covers vuer_oss / vuer_css — this note is the esign_css-specific counterpart.

Customization Branch Fleet (2026-05)

Most esign_css customization branches are archived

Only one esign_css customization branch is actively maintained. Treat the rest as historical unless proven otherwise.

Branch	Status	Last Touched	Notes
customization/instacash	Active	2025-11-20	The only live MBH-family esign_css branch
customization/minikolcson	Archived	2019-04-08	—
customization/cofidis	Archived	2019–2021	—
customization/sberbank	Archived	2019–2021	—
customization/cig	Archived	2019–2021	—
customization/equilor	Archived	2019–2021	—
customization/mikrocredit	Archived	2019–2021	—
customization/raiffeisen	—	—	Only esign_css branch with a customization/docs/ directory (see below)

customization/instacash

• The only active MBH-family esign_css customization branch.
• As of 2026-05 it is 52 commits behind devel, with breaking changes queued on devel:
  • Express upgrade — FKITDEV-8185
  • RPC refactor — FKITDEV-4645
  • ESLint 9 migration
• devel → instacash updates land via update/customization/instacash-{date} PRs.
• Recent cadence is roughly quarterly:
  • 2025-08-18 → release 1.3.0.9
  • 2025-11-12 → release 1.3.0.10
• Release history lives in customization/instacash:customization/RELEASE.md.

customization/raiffeisen — the only branch with docs

customization/raiffeisen is the only esign_css branch that ships a customization/docs/ directory:

File	Contents
dev.md	eSign dev-environment setup + testing guide (see method below)
Konfigurációs értékek.md	Annotated config-value reference

Dev / Test Method (from customization/docs/dev.md)

esign_css is NOT tested standalone

You test esign_css through VÜER CSS, not on its own.

Steps

1. In VÜER CSS config, set development.requestFakeCustomer = true.
2. Restart VÜER CSS.
3. Open VÜER CSS with query params: ?esign=1&token=<customerId>.
4. If the customer is “Aláírásra vár” in VÜER and “engedélyezett” in eSign OSS and has an uploaded offer, VÜER redirects to eSign CSS /agreement-checks.

After any branch switch inside the esign_css container

Mandatory rebuild sequence:

yarn && yarn build && supervisorctl restart all

Related

• esign — Electronic Signature System overview (esign_css / esign_oss)
• FKITDEV-8817 — esign_css jQuery vuln remediation
• customization-branches — vuer_oss / vuer_css customization branch index
• release-process — FaceKom release process