CRATEFIELD
Get started with Harness Join the waitlist

adapter-cloudflare-saas

CustomHostnames over the Cloudflare for SaaS custom-hostnames API.

With cargo

cargo add cratefield-adapter-cloudflare-saas
crates.iodocs.rsSource

What it is

adapter-cloudflare-saas.

CustomHostnames port over Cloudflare for SaaS custom hostnames (issue #590) for the Cratefield harness. Uses the runtime's HttpClient port — no reqwest, no vendor SDK — so it runs unchanged on Workers (worker::Fetch) and natively, and inherits that port's destination vetting, deadline and response-size caps.

From the crate’s own README.

Ports

Implements CustomHostnames

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 4 versions recorded, newest first. Every published version is on crates.io.

  1. 0.2.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core

  2. 0.2.1

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
2 earlier versions 0.1.0 to 0.2.0

  1. 0.2.0

    crates.ioReleaseDiff

    Changed

    • Breaking: requires cratefield-core 0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).

    Other

    • updated the following local packages: cratefield-core

  2. 0.1.0

    crates.ioRelease

    Other

    • CustomHostnames port in core, with a Cloudflare for SaaS adapter (#590) (#630)

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules