Authentication and licensing: UAT roadmap progress
Login, recovery, licensing and the collaborator journey verified in UAT, including server rejection of writes and foreign-kitchen selection. Remaining integrations and PROD are pending.
Read post → Infrastructure team journal
Operational history
Incidents, infrastructure changes, maintenance and service updates, preserved as a chronological and permanent record.
Identity, authorization and licenses: consolidation prepared for UAT
The API, app, CRM, ADM and FIC received coordinated identity and access rules. Tests passed and five UAT images were published; deployment and authenticated acceptance remain pending.
Read post →Kulinaryos authentication consolidated: passwords, Google and recovery
How we stabilized access to existing accounts, released direct Google sign-in through ZITADEL, and verified Brevo password recovery.
Read post →Kulinaryos identity: infrastructure live, central sign-in under test
Password recovery, legacy sign-in and central login return were verified with a controlled account; Google remains in testing and the investigation continues.
Read post →Investigating Kulinaryos authentication
The access diagnosis is ongoing. The central identity plan with Go and ZITADEL includes username and password or Google sign-in, with safe account linking.
Read post →DNS incident affecting the Gara test platform
gara.kulinaryos.com became unreachable because its DNS record was absent from the migrated authoritative zone. The record was restored and the platform is reachable again.
Read post →Institutional website recovered in the RBX cluster
A static replica of the WordPress frontend is now served through the RBX Traefik edge, removing the immediate dependency on the origin that was blocking connections.
Read post →Institutional website connectivity incident
The legacy WordPress origin refused connections from RBX egress addresses. Service was restored through a controlled relay while the root cause is investigated.
Read post →Kulinaryos DNS infrastructure alignment
The authoritative nameservers move to RBX without changing the application servers, email, or the existing workflow.
Read post →