AI Signal 185
datasette-publish-fly 1.4 forces HTTPS, fixes volume lookup, accepts app-scoped tokens
↗
Illustration only Photo by Ivan N on Unsplash
datasette-publish-fly 1.4 sets force_https=true in fly.toml, fixes a Volume could not be found bug, and is compatible with app-scoped deploy tokens.
For engineers publishing Datasette instances to Fly, this release hardens deployments by forcing HTTPS and resolves a volume attachment failure that could break persistence. The token compatibility update also simplifies CI/CD pipelines that use scoped credentials.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
force_https=true is now set in fly.toml, ensuring all traffic to the deployed app is redirected to HTTPS.
The release fixes the 'Volume could not be found' bug, which previously prevented attaching persistent volumes.
App-scoped deploy tokens are now supported, allowing more granular permissions for automated deployments.
THE CLUSTER