App service
Services/Varnish

Varnish service

HTTP caching service built on Vinyl, the new name for Varnish, for accelerating responses in front of web applications.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

Overview

Technical profile and packaging

This page shows how Varnish is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

8.0, 6.0

Ports and protocols

6081/HTTP

Labels

varnish

Stacks

Use it inside ready-made stacks or your own

This service is available as a reusable building block even when it is not currently exposed by one of the public stacks.
Build a custom stack around Varnish when you want this service without the constraints of a predefined stack.

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

6081/HTTP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Configs

2 configs can be versioned with the service.

Service links

These links define which other services can connect to Varnish when it is used inside a stack.

Derived services

Build your own service on top of Varnish

These services already extend Varnish. They show how the same base runtime can be turned into more specialized building blocks without rebuilding everything from scratch.

Replacement

Vinyl is the modern replacement for Varnish

The open source Varnish project changed its name to Vinyl. If you want the current community-driven continuation, use the Vinyl service as the direct replacement.