Activity

Summary

• Fix 502 errors on cleaner dashboard — nginx was returning 502 after Stripe Connect redirects because the response headers exceeded the default 4KB fastcgi buffer. Added fastcgi_buffer_size 32k and fastcgi_buffers 16 16k to the nginx template in nixpacks.toml.
• Add implementation plans for the two remaining release features:
  • docs/plans/direct-booking-implementation.md — client books cleaner directly from profile (reuses JobPosting with new source column)
  • docs/plans/calendar-availability-implementation.md — cleaner availability schedule + calendar view
  • docs/plans/testing-plan.md — pre-release test coverage review and verification checklist

Root Cause (502)

upstream sent too big header while reading response header from upstream

Found in /var/log/nginx-error.log inside the container. Happens on GET /cleaner/dashboard when referred from https://connect.stripe.com/ — the Stripe Connect callback stuffs session flash data that pushes response headers past nginx's default 4KB buffer limit.

Test plan

• Deploy and verify cleaner dashboard loads after Stripe Connect redirect (no more 502)
• Review plans for direct booking and calendar features
• Note: nixpacks should be replaced with a proper Dockerfile — this is a band-aid on a config we don't fully control