mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-05-22 18:51:27 -05:00
cc2fe6bbff
Three bugs in the original workflow surfaced on first run: 1. mage build failed because the API binary embeds frontend/dist/* and no placeholder existed. Mirror the parent workflow's `mkdir -p frontend/dist && touch frontend/dist/index.html` step. 2. Backgrounded ./vikunja web didn't survive the step boundary. The parent's frontend e2e job sidesteps this by running the API + tests in a single shell; do the same here, with nohup + an EXIT trap so the API is killed even if the test step crashes. 3. user1/12345678 doesn't exist on a fresh sqlite-memory DB — fixtures are only loaded by tests that explicitly seed them. Register a throwaway e2eadmin via POST /register before invoking mage test:e2e. service.enableregistration defaults to true, so no extra config. Also: chmod +x ./vikunja explicitly, bump installed mage to 1.17.2 to match veans/go.mod, and upload /tmp/vikunja.log on failure for next time.