5f81f7c179acca9801a487e71dae970914d8ce82
Without the trailing slash the browser resolves relative asset URLs (style.css, player.js) against /file/, producing 404s. Also switch the patch target from the obsolete /play/ scheme to the /file/ route the API actually serves. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
love-tools
CI/CD templates for LÖVE (Love2D/Lua) game projects, in the same spirit as tic80-tools.
example-makefile.make— project Makefile: local dev targets (build,love,web,export,watch,clean) plus the Woodpecker pipeline targets (ci-version,ci-export,ci-upload,ci-update).example-woodpecker.yaml— Woodpecker pipeline: version → export (.lovepackage + love.js web build) → upload (scp to the droparea) → update (calls the teletypegames/updateendpoint withplatform=love).example-tasks.json— VS Code.vscode/tasks.jsonwith the common dev tasks: Run Löve (love ., default build task,Cmd+Shift+B), Build & Run Löve, Build .love package and Make build.
Usage in a game repo
- Copy
example-makefile.maketoMakefileand setPROJECT(the package is built asdist/$(PROJECT).love). - Copy
example-woodpecker.yamlto.woodpecker.yamland add thedroparea_ssh_password/update_secret_keysecrets in Woodpecker. - Copy
example-tasks.jsonto.vscode/tasks.json.
The pipeline uploads $(PROJECT)-$(VERSION).love.zip,
$(PROJECT)-$(VERSION).html.zip and the versioned metadata.json to
the droparea, then triggers /update twice: once with platform=love
(desktop package) and once with platform=love-web (web build).
Detailed documentation lives on the wiki: /development/love.
Languages
Makefile
81.8%
Dockerfile
18.2%