App service
Services/Gotenberg

Gotenberg service

Document conversion and PDF generation service for applications that need server-side rendering workflows.

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

On Wodby

How Gotenberg runs on Wodby

What Wodby sets up for this Gotenberg service. It runs the official gotenberg/gotenberg image, an HTTP API that converts web pages, HTML, Markdown and office documents to PDF.

How applications reach it

  • Base URL: http://<app service name>:3000. No TLS and no authentication is configured; no token is generated.
  • No catalog service declares a link to it, so no variable with its address is set automatically. Put the base URL into the application's own configuration or a variable of the application service, and read it from there.
  • Conversions are multipart POST requests to a route per conversion type, for example /forms/chromium/convert/url, /forms/chromium/convert/html (with an index.html file) and /forms/libreoffice/convert. A client written for another PDF service does not work by changing only the host and port.

Things that matter in an environment

  • Gotenberg fetches the page itself. A URL passed for conversion must be reachable from the Gotenberg container: use an address that resolves inside the environment or a public one, and pass cookies or headers the page needs with the request.
  • The service is stateless, has no volume and can run several replicas. Results are returned in the response; nothing is kept.
  • The manifest sets no Gotenberg options: timeouts, API basic authentication and other settings are Gotenberg's own flags and environment variables, set on this service.

Check the result

  • GET http://<app service name>:3000/health answers 200 with the status of the conversion engines.
  • GET http://<app service name>:3000/version returns the running version.

Basic auth

Wodby protects this service's public domains with basic auth by default, because Gotenberg has no authentication of its own and fetches the URLs it is given. Each app service of it gets its own generated password, which members reveal on the environment's Endpoints > Auths page. Applications inside the environment call it directly and need no credentials; only clients outside the environment send the username and password.

Overview

Technical profile and packaging

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

Ports and protocols

3000/HTTP

Labels

gotenberg, print

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Gotenberg 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.

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

3000/HTTP

Technical domains

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