Daeseon Yoo
Back to project
·Troubleshoot·2 min

First deploy night — Railway + auto-migration, dynamic PORT, Dockerfile fixes, energy-beam finish

First-deploy night on Railway — added a Dockerfile and railway.toml with auto-migration, fixed dynamic PORT binding and Dockerfile COPY order, and shipped the dramatic match-finish energy-wave beam.

What happened

First deploy night for Ki Clash on Railway, with some front-end polish on either side of the deploy work.

The deploy setup landed in a few steps:

Note: no error text or specific failure symptom appears in any commit subject (only "debug: log migration status"), so none is reproduced here.

Front-end polish around the deploy

Earlier the same night, animations were slowed down and fighters made to animate independently (bac38a5), then dynamic fighter animations with per-action effects were added (8309958) — the polish leading into the deploy.

After the deploy config, the dramatic match finish and a visible energy-wave beam shipped across the battle/effects front-end (547925f), touching BattleArena, PixelEffects, PixelFighter, and pixel-art-types.

Housekeeping

Notes

Commits