Inline edge functions and visitor geolocation, CDN setup for Coolify applications, User-Agent matching in page rules, CAPTCHA support for forms, and a CLI publish command.
The Quant CLI has a new publish command for publishing a path from the command line. It publishes the latest revision by default, or a specific revision with the --revision option, and is available from CLI version 4.0.0.
The crawl command now accepts a --user-agent flag, so you can set the user-agent string sent with crawl requests. It defaults to the standard Quant crawler user-agent and is available from CLI version 4.0.0.
New Edge functions
Inline functions in pages
You can now embed the output of an edge function in a page. Add a {{QUANT_FN:UUID}} token with the function's UUID to the page markup. When the page is served, Quant replaces the token with the function's output. For content served from Quant, turn on "Enable inline functions" in the project settings. For HTML responses from your origin, select "Allow inline functions" on a proxy rule.
Edge functions can now read the visitor's location from event.geo, including the country, region, city, postal code, latitude, longitude, and the network (AS) name and number. You can use it to show content for the visitor's country, such as a consent notice, or to redirect visitors to a local edition of your site. The edge functions documentation lists every field.
You can now protect your forms with reCAPTCHA v2, alongside the existing automatic spam detection controls. Add your reCAPTCHA secret key to the form settings. Quant then verifies the challenge response with each submission and does not store the challenge response with the form data. A setup guide is available in the documentation.
You can now add the Quant CDN to an application that you host with Coolify. Choose Coolify in the new project wizard, connect to your Coolify server with a read-only API token, and select the Coolify project and environment. The wizard fills in the domains and origin settings that it can detect from your Coolify application, and you can change them before you create the project.
New Rules
User-Agent matching
Page rules now support matching on the request User-Agent header. You can configure a rule to apply when the User-Agent is one of a set of values, or when it is not one of them. This gives you finer control over which requests a rule targets. Matches are case insensitive and support the * wildcard in values.
The content code editor now has Save and Preview buttons. Save publishes the editor contents as a new revision, the same as the existing F1 menu command and the Ctrl+S or Cmd+S shortcut. Preview renders the markup you are editing in a preview window, so you can check the page before you save it. The edge function editor also gets the Save button.
Improved GitHub Actions
CI/CD deployment guide
A new guide in the documentation shows how to build a static site and deploy it to Quant with GitHub Actions. The example workflow deploys a development branch and a production branch to separate projects, and keeps your API tokens in GitHub secrets. It uses a revision log to skip files that did not change, and purges the project cache after each deployment.
You can now turn on image optimisation when you create a project, instead of only in the project settings afterwards. The option is in the project setup wizard for CDN, static site, snapshot, Drupal and WordPress projects, and you can also try image optimisation during a trial.
Improved Rules
Serve static content from the incoming path
Serve static content rules can now use the special /$* value to serve static content from the same path as the incoming request, rather than pointing every matched request at a single fixed path.
Content at URLs longer than 500 characters was not stored or served correctly. Some uploads of content to these URLs failed with an error. Quant now stores and serves content at these URLs reliably.
Fixed Forms
Submissions with file uploads
On some projects, submissions from forms with a file upload field did not save correctly. These submissions now save correctly, and the uploaded files are stored with the submission.