Commit graph

3 commits

Author SHA1 Message Date
Ashwin Kumar Sivakumar
e2635c1c30 fix(migrate): fix db-migrate build and job manifest, both broken
Some checks failed
build-and-release / build (cron) (push) Successful in 49s
build-and-release / build (catering-services) (push) Successful in 1m35s
build-and-release / build (companies) (push) Successful in 1m38s
build-and-release / build (graphic-designers) (push) Successful in 9s
build-and-release / build (developers) (push) Successful in 2m4s
build-and-release / build (customers) (push) Successful in 2m16s
build-and-release / build (employees) (push) Successful in 2m20s
build-and-release / build (gateway) (push) Successful in 57s
build-and-release / build (job-seekers) (push) Successful in 1m39s
build-and-release / build (fitness-trainers) (push) Successful in 2m46s
build-and-release / build (photographers) (push) Successful in 9s
build-and-release / build (jobs) (push) Successful in 1m43s
build-and-release / build (leads) (push) Successful in 1m40s
build-and-release / build (makeup-artists) (push) Successful in 2m28s
build-and-release / build (tutors) (push) Successful in 1m23s
build-and-release / build (payments) (push) Successful in 2m51s
build-and-release / build (social-media-managers) (push) Successful in 2m33s
build-and-release / build (ugc-content-creators) (push) Successful in 2m23s
build-and-release / build (users) (push) Has been cancelled
build-and-release / build (video-editors) (push) Has been cancelled
Dockerfile.migrate copied only crates/db-migrate + a few unrelated crates
but left the root Cargo.toml's [workspace] members list referencing every
apps/* service, none of which exist in this build context - cargo failed
immediately with "failed to load manifest for workspace member apps/gateway".
Trim the workspace to just crates/db-migrate (it has no path dependency on
anything else per crates/db-migrate/Cargo.toml) using the same awk trick
Dockerfile.simple already uses per-service. Also fix the resulting binary
output path (workspace builds put target/ at the workspace root, not under
the member crate's own directory).

k8s-migration-job.yaml targeted namespace: default, where neither
nxtgauge-backend-rust-secrets nor a registry pull secret exist - both only
exist in the nxtgauge namespace where the actual app runs. Fix the namespace
and add the missing imagePullSecrets so the job can actually pull its image
and read DATABASE_URL.

Neither of these had ever been exercised successfully before - this is the
first real migration run since the job/image were added.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-19 03:07:26 +05:30
Ashwin Kumar Sivakumar
b8939e6384 fix(k8s): switch db-migrate image from GHCR to Forgejo registry 2026-07-06 03:52:54 +05:30
Tracewebstudio Dev
63eb27a160 fix(auth): accept both full_name and first_name+last_name for backward compatibility
RegisterPayload now accepts:
- full_name (single field, for old frontend clients)
- first_name + last_name (new format)

Error returned only if none of these are provided.
2026-04-13 19:59:48 +02:00