Depado / pb-templ-htmx-tailwind

POC with PocketBase, Templ, HTMX and Tailwind
MIT License
5 stars 3 forks source link

pb-templ-htmx-tailwind

POC with PocketBase + Templ, HTMX + hyperscript and Tailwind + daisyUI

Roadmap

Development

Requirements

Once these two requirements are met:

$ make deps
$ make

VSCode debug

The .vscode folder is configured to add a Run and a Debug launch commands.

Build workflow

Live mode

$ go install github.com/bokwoon95/wgo@latest
$ make live

Live mode profits from Make's multi-process abilities by running three commands in parallel:

This will start templ's hot reload server that allows to automatically refresh the page whenever a template changes without restarting the server. Modifying the templates also changes the CSS file and triggers a page reload by sending a payload to templ's hot reload server. Whenever a go file that is not a templ generated file is changed, the backend restarts too.

Live mode also disables browser caching by setting the Cache-Control header to "no-store" for assets. This ensures the main CSS file is not cached when templ hot reloads the page.

Docker

$ docker build -t ptht:latest .
$ docker run --rm -p 8080:8080 -v $PWD/dockerdata/pb_data:/pb_data --name ptht ptht:latest
Details & tricks #### Bun in Go docker image As shown in the build workflow section, this project requires both templ, bun and Go to be run in a sequential order. At first a four stage Dockerfile was created: - Using first `golang:alpine` to install templ and generate templ go files - Then using `oven/bun:alpine` to build the CSS based on templ go files - Then back to using `golang:alpine` for the rest of the build - Installing dependencies, embedding assets and building - Then using `gcr.io/distroless/static` to serve The main issue was that the whole build directory was copied over from one step to another and the cache was invalidated way too often. The Dockerfile was switched to using `golang:debian` (because Bun can't be installed on alpine distros without glibc) and the bun setup script was used, which greatly improved caching but removed the ability to automatically bump bun's version using Renovate. In the end the chosen solution was to use the `oven/bun:debian` image as a first step and copy over the bun binary to the build step. This way the bun version is pinned and can be upgraded using renovate.