| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 500 | 10 Feb 2026 | |
| latest/stable | 499 | 10 Feb 2026 | |
| latest/stable | 498 | 10 Feb 2026 | |
| latest/stable | 346 | 14 Mar 2024 | |
| latest/stable | 345 | 14 Mar 2024 | |
| latest/stable | 344 | 14 Mar 2024 | |
| latest/stable | 341 | 14 Mar 2024 | |
| latest/stable | 340 | 14 Mar 2024 | |
| latest/stable | 334 | 14 Mar 2024 | |
| latest/stable | 91 | 01 Feb 2022 | |
| latest/candidate | 385 | 11 Sep 2024 | |
| latest/candidate | 384 | 11 Sep 2024 | |
| latest/candidate | 383 | 11 Sep 2024 | |
| latest/candidate | 346 | 14 Mar 2024 | |
| latest/candidate | 345 | 14 Mar 2024 | |
| latest/candidate | 344 | 14 Mar 2024 | |
| latest/candidate | 23 | 08 Apr 2021 | |
| latest/beta | 437 | 07 Dec 2024 | |
| latest/beta | 436 | 07 Dec 2024 | |
| latest/beta | 435 | 07 Dec 2024 | |
| latest/beta | 346 | 14 Mar 2024 | |
| latest/beta | 345 | 14 Mar 2024 | |
| latest/beta | 344 | 14 Mar 2024 | |
| latest/edge | 426 | 02 Dec 2024 | |
| latest/edge | 425 | 02 Dec 2024 | |
| latest/edge | 424 | 02 Dec 2024 | |
| latest/edge | 423 | 02 Dec 2024 | |
| latest/edge | 385 | 11 Sep 2024 | |
| latest/edge | 384 | 11 Sep 2024 | |
| latest/edge | 383 | 11 Sep 2024 | |
| latest/edge | 346 | 14 Mar 2024 | |
| latest/edge | 345 | 14 Mar 2024 | |
| latest/edge | 344 | 14 Mar 2024 | |
| latest/edge | 89 | 13 Jan 2022 | |
| 1/stable | 467 | 08 Aug 2025 | |
| 1/edge | 512 | 20 Apr 2026 |
juju deploy content-cache --channel 1/edge
A charm for managing a content cache with nginx.
<!-- Avoid using this README file for information that is maintained or published elsewhere, e.g.: * metadata.yaml > published on Charmhub * documentation > published on (or linked to from) Charmhub * detailed contribution guide > documentation or CONTRIBUTING.md Use links instead. -->
<!-- vale Canonical.007-Headings-sentence-case = NO -->
Content Cache Operator
<!-- vale Canonical.007-Headings-sentence-case = YES -->
A Juju charm deploying and managing a static web content cache with nginx.
This machine charm manages a nginx instance configured as a content cache. The configuration for the locations of cache is managed with the Content Cache Backends Config subordinate charm. Each Content Cache Backends Config charm stores the configuration for a location and the associated set of backends.
This charm should be used for caching static web content. When a client makes a request, this charm checks if the requested content is cached and valid. If not this charm will query the backends hosts for the content to refresh the cache. This process works well for static content that does not change based on the client. For this type of content, the cache can greatly reduce the load on the backend hosts.
The charm simplifies the operation of an nginx server as a static web content cache. This makes the charm suitable for users looking for a low maintenance way to reduce load on static websites.
For more information see the Content Cache charm.
Get started
To begin, refer to the Content Cache tutorial for step-by-step instructions.
Integrations
You can find the full list of integrations in the Charmhub documentation.
Learn more
Project and community
The Content Cache Backends Config Operator is a member of the Ubuntu family. It is an open source project that warmly welcomes community projects, contributions, suggestions, fixes and constructive feedback.