App service

Nginx service

Web server and reverse proxy service for routing HTTP traffic to application runtimes.

Use it as a versioned stack building block that can build from source, plug into CI/CD, and connect to external providers without hardcoding secrets into the codebase.

All services

Why teams use this service

Technical profile

Review versions, ports, source, and packaging.

Stacks that use it

See where this service fits in ready-made stacks.

Source builds and CI/CD

Build from Git, use Wodby CI, and publish images cleanly.

Runtime wiring and defaults

See ports, links, storage, configs, and runtime behavior.

Build on top of this service

See derived services that extend the same runtime.

Overview

Technical profile and packaging

This page shows how Nginx 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

1.29, 1.28, 1.27, 1.25

Source repository

wodby/service-nginx

Public Helm chart

wodby/nginx

Ports and protocols

80/HTTP

Labels

nginx

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Nginx as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

HTML

CI/CD

Build from source and ship changes without extra glue work

Nginx can build from source as part of a stack. Connect your repository, start from a public build template when one exists, and keep CI/CD and image storage inside the same Wodby workflow.

React boilerplate

Start from a working boilerplate instead of wiring the build process from scratch.

wodby/react-boilerplate

Git providers

Connect repositories from supported Git providers when this service should build from your own codebase.

BitBucket GitHub GitLab

CI providers

Wodby CI is the default path, but external CI providers can fit the same build and release workflow when that suits your team better.

Wodby CIUsed by defaultBuilt into the standard Wodby CI flow for buildable services.Circle CI

Container registries

Keep built images in Wodby Registry by default or store them in another registry without changing how the service is built.

Wodby RegistryUsed by defaultThe default private registry for images built through Wodby.Distribution Registry Docker Hub

Keep secrets and variables outside the codebase

Attach provider credentials and environment variables at the platform level so the build and runtime do not depend on hardcoded secrets.

Algolia AWS Anthropic Auth0 Cloudflare Discord Gemini Intercom Mailchimp New Relic OpenAI Pusher Sentry Slack Stripe Telegram Twilio

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

80/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.

Settings

1 setting can be overridden per environment.

Service links

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

Derived services

Build your own service on top of Nginx

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

Nginx (Matomo)Nginx (PHP)