Remote URL lists
A crawl can now be seeded from a remote URL list. Provide a URL to a hosted list of paths and the crawler will fetch it and add those paths to the crawl, in addition to any configured start URLs.
Changelog · 2025-08
Application proxy support across the dashboard, API and Terraform provider, and crawler webhook authentication and support for remote URL lists.
14 updates across 7 products shipped this month.
A crawl can now be seeded from a remote URL list. Provide a URL to a hosted list of paths and the crawler will fetch it and add those paths to the crawl, in addition to any configured start URLs.
A new GitHub Action, quantcdn/quant-cloud-init-action, initialises Quant Cloud deployments in your workflows. It determines the environment name from the branch, tag or pull request, and signs in to the Quant Cloud image registry automatically. It also validates the organisation and application, and outputs image tag suffixes and a production flag for later steps. You can override the application, the master branch and the environment name. The master branch is the branch that the action maps to the production environment. By default, this is main or master.
Related documentation: Init Action
When you create an application, you can now choose a template from the Import from GitHub Template list instead of writing a Docker Compose file. The dashboard imports the template's compose file, so you can deploy WordPress, Drupal, Drupal CMS, Laravel or a PHP application in a few steps. The templates are public repositories in the quantcdn-templates GitHub organisation. To link directly to one, add ?template=<repository name> to the create application page address.
Related documentation: Start from a template: Create a cloud application from a template
You can now run an environment in single-task mode, so only one container runs at a time. The minimum and maximum instances are then locked to 1. Use it for applications such as MongoDB that use lock files or need exclusive access to their data. Select Enable Single Task Only Mode when you create an application or environment, or when you edit an application. When an imported Docker Compose file contains an image that needs this mode, the create application form turns it on for you.
Related documentation: Manual Scaling (Fixed Instance Count): Single-Task Mode
You can now configure an application proxy through the rules API. The dashboard rule editor already offers this option. An application proxy is a proxy rule that sends requests to a container port in one of your Quant Cloud application environments. You choose the application, environment, container and port, and Quant sets the origin address and host header. Standard proxy rules still support an optional host header override and a configurable origin timeout, as before.
Related documentation: Releasing Your Application on a Custom Domain: Step 4: Set Up Proxy Rules
The Terraform provider can now create and manage application proxies, so you can declare them in code with the rest of your Quant project configuration. Set application_proxy = true on a quant_rule_proxy resource, with the application_name, application_environment, application_container and application_port arguments. You can also set the origin timeout on any proxy rule with the new origin_timeout argument on the resource.
The CLI can now delete redirects, so redirect clean-up can be scripted alongside creation without opening the dashboard.
Related documentation: quant redirect: Delete a redirect
You can now configure crawler webhooks through the crawler API. Webhooks now also support an authentication header, in addition to the webhook URL and custom variables. The endpoint that you trigger when a crawl completes can use this header to verify the request.
Related documentation: Crawler: Webhooks
The dashboard upload limit has been increased to 256 MB.
Plans and applies that create, update or delete many rule resources at once now complete reliably. The provider now makes these rule changes one at a time, while other resources still apply in parallel. Separately, the updated_at attribute of the quant_crawler resource now shows the latest value from the API after each change.
Cache lifetime now accepts both string and integer values in your configuration. The host header field is now optional, and a changed origin timeout is saved when you update a rule. These are the quant_rule_proxy arguments cache_lifetime, host and origin_timeout.
The crawler now runs one bulk cache purge at the end of a crawl instead of purging each item.
Upload and bulk upload showed an error for files whose checksum already matched the stored copy. These files are now reported as uploaded. HTML files that use a character encoding other than UTF-8, such as Windows-1252, no longer cause an error.
When creating a new environment from an existing one, configured health-check commands were not carried over. Health-check items are now cloned into the new environment form, with fixes to how health-check changes are saved.
No updates for that product this month.