HOCO B2B
Team tasksAnis

LCH-01 — Production go-live — deploy, import data, monitoring

Production deploy, initial import of products/resellers/users, monitoring and alerting live, apps published on the Play closed track for pilot users.

FieldDetails
Task codeLCH-01
PhaseP2 — Acceptance, go-live & pilot
Product scopeV1
StatusPlanned
StartMon 28 Dec 2026
DueTue 29 Dec 2026
ResponsibleAnis — Full-stack developer
Co-responsibleImad
Effort1 person-day(s) planned · 3 from scratch · size S
Area · appLaunch · ops
Depends onQA-02
UnblocksLCH-02
MilestonesProduction go-live

Summary

Production deploy, initial import of products/resellers/users, monitoring and alerting live, apps published on the Play closed track for pilot users.

Description

After the signed PV, the platform goes to production (cahier §13.2; OPS-02, ADM-06, NFR-08). This task deploys the accepted release from a master tag, switches the final domains, configures production secrets (FCM, SMS sender, email, storage), imports HOCO's products, resellers, users and stock through the import jobs (dry run, then apply), sends staff and delegates their password-setup links, turns monitoring and alerting on, verifies production backups, and publishes both apps on the Play closed track for pilot users. A go/no-go checklist and a rollback plan frame the day. Out of scope: training (LCH-02) and the pilot run (LCH-03).

Subtasks

#SubtaskOwner
1Go/no-go checklist and rollback plan (previous image tag, database snapshot before import)Anis
2Production deploy from the master tag; migrations; smoke testsAnis
3Final DNS and TLS for api, app (reseller web) and back-office domainsAnis
4Production secrets and providers: FCM production project, SMS sender id, email domain (SPF/DKIM), storage bucketsAnis
5Initial imports with HOCO's files: products (three prices, attributes), resellers (customer types), users, stock — dry run, fixes, applyAnis
6Settings, reference lists and support regions set to the values closed in PRJ-03 and QA-02Anis
7Monitoring live: Sentry projects, uptime checks, queue depth and dead-job alerts, backup verificationAnis
8Publish reseller and delegate apps on the Play closed track with production configuration; add pilot testersImad

Deliverables

  • Production Dokploy apps hoco-api, hoco-worker, hoco-dashboard, hoco-web running the accepted release
  • Import reports for products, resellers, users and stock
  • Go-live checklist signed off; monitoring dashboards and alert routes

Acceptance criteria

  • Production health checks pass and the smoke suite runs green against production (OPS-02)
  • Imported counts match HOCO's files, with rejected rows explained (ADM-06)
  • Staff and pilot delegates can sign in with their own passwords
  • An alert fires and reaches Anis when the api is stopped for the test (NFR-08)
  • Pilot users can install both apps from the Play closed track and sign in to production

Requirements covered

RequirementTitleRelease
OPS-02Deployment: server, database, storage, backups, domains, certificates, external services, store publicationV1
ADM-06Initial imports: products, resellers, user accounts, stockV1
NFR-08Logging of sensitive actions and technical errors; monitoring and alertingV1

Test measures

  • Production smoke suite (sign-in, catalog, checkout to SUBMITTED, confirmation, SSE event)
  • Alert test by stopping a non-critical process
  • Backup of the first production night verified

Risks

  • Import data quality (duplicates, missing prices or attributes) — dry runs on HOCO's files during QA-02, not on go-live day
  • Play review delays for the closed track — submit builds a few days before go-live

KPI

  • Delivered by Tue 29 Dec 2026 within 1 person-day(s).
  • Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
  • Zero open critical defects, permission gaps or data-integrity regressions at sign-off.

Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.

On this page