BPPP/smb-online
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

Per-client Easy!Appointments isolation #9

New Issue
Closed
opened 2026-07-16 10:37:37 +02:00 by mivanchenko · 1 comment
mivanchenko commented 2026-07-16 10:37:37 +02:00
Owner
Copy Link
Copy Source

Today booking runs a single shared Easy!Appointments instance (deploy/booking/). For real multi-client operation, isolate per client (separate EA instance/DB per client stack, mirroring the per-client nginx compose approach) so providers, services, and data don't bleed across clients.

Acceptance: two clients can be onboarded with fully separated booking data and admin logins.

Today booking runs a single shared Easy!Appointments instance (`deploy/booking/`). For real multi-client operation, isolate per client (separate EA instance/DB per client stack, mirroring the per-client nginx compose approach) so providers, services, and data don't bleed across clients. **Acceptance:** two clients can be onboarded with fully separated booking data and admin logins.
mivanchenko added the bookingenhancement labels 2026-07-16 10:37:37 +02:00
mivanchenko added the needs-triage label 2026-07-23 10:31:45 +02:00
mivanchenko commented 2026-07-23 11:34:10 +02:00
Author
Owner
Copy Link
Copy Source

This was generated by AI during triage.

Superseded by the decision to build a single multi-tenant booking app with logical client_id isolation instead of per-client Docker stacks. Physical per-client isolation is kept only as a possible future paid exception (data-residency premium), not the default. Closing.

> *This was generated by AI during triage.* Superseded by the decision to build a single **multi-tenant** booking app with logical `client_id` isolation instead of per-client Docker stacks. Physical per-client isolation is kept only as a possible future *paid* exception (data-residency premium), not the default. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
booking
Booking / Easy!Appointments
 bug
Something is broken
 crm
Back office / CRM
 enhancement
New feature or request
 infra
Infrastructure
 n8n
n8n workflows
 needs-info
Waiting on reporter for more information
 needs-triage
Maintainer needs to evaluate this issue
 ops
Operational / runtime
 ready-for-agent
Fully specified, ready for an AFK agent
 ready-for-human
Requires human implementation
 security
Security / secrets hardening
 tech-debt
Refactor / debt
 wontfix
Will not be actioned
No Label booking enhancement needs-triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Administrator mivanchenko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: BPPP/smb-online#9
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?