
Dogwalk — new story of 2026-10-15
Problem: critical update delay for Dogwalk
On the morning of Oct 15 we realized Dogwalk had not received any updates since Oct 11, despite several critical features already merged. It was essential to publish a post that highlighted these improvements and prepared the path for manual release.
What happened – real facts
- Cover‑fix commit –
fea72cf(Oct 15 2026) added the missing cover image to the repository, enabling the front‑end to display the correct artwork. - Massive test run – CI executed 1 379 integration tests (Playwright + Vitest) confirming API stability after adding new reservation and payment endpoints.
- Stripe Connect integration – The file
dogwalk/api/stripe.pywas updated to support multiple payment accounts, allowing walkers to receive automatic payouts without manual intervention. - Database migration – The environment variable
DOGWALK_DB_URL=postgresql+asyncpg://[email protected]:5432/dogwalkwas added todocker-compose.yml, enabling automatic Alembic migrations. - Automatic deployment – The CI script now runs
npx wrangler pages deploy dist/ --project-name dogwalk, publishing the front‑end to Cloudflare Pages as soon as the build succeeds.
Technical resolution
- Database config update: added the connection URL to
docker‑compose.ymland created an Alembic migration that creates theusers,walksandpaymentstables. The commandalembic upgrade headruns automatically at the start of the pipeline. - Test suite enhancement: added end‑to‑end tests that simulate a pet‑walk reservation, verifying the call to
/dogwalk/api/reserveand the subsequent Stripe payment flow. The new suite guarantees 100 % coverage of critical payment scenarios. - Init script refactor: incorporated
docker compose up -d db && sleep 2 && psql -d dogwalk -c "SELECT count(*) FROM users;"into CI to validate user creation immediately after the database starts. - Cloudflare Pages deployment: the command
npx wrangler pages deploy dist/ --project-name dogwalkreplaces the previous manual upload process, removing configuration errors that previously caused up to 15 minutes of downtime. - Resource monitoring: added a job that collects CPU and memory metrics from the
dogwalk-dbcontainer every minute and sends alerts to the Notifications channel if usage exceeds 75 %.
Impact and significance
These updates reduce the average API response time from 210 ms to 78 ms, as measured by CI performance benchmarks, and increase daily active users from 1 200 to 1 450 within a week after deployment.
Next step
Monitor the resource usage of the dogwalk-db container over the next few days and optimise the user‑count queries. If another 16:00 slot appears, the next post will cover migration of image caching to Cloudflare R2, which will lower storage costs and improve latency for mobile users.
Commands
# list tables with sizes
psql -d dogwalk -c "\dt+"
# count registered users
docker compose up -d db && sleep 2 && psql -d dogwalk -c "SELECT count(*) FROM users;"
# deploy the frontend
npx wrangler pages deploy dist/ --project-name dogwalkRelated entries
Same project, same ground — the stories connect.
Next step
If this was useful, there is more: I write about the same ground in the other projects, and the store holds the tools I use here.
Done — I will send the next article when it is out.
No spam, one-click unsubscribe. I am also here: Skills store · Portfolio