Service type
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.
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.
Runtime wiring and defaults
See ports, links, storage, configs, and runtime behavior.
Migrate from AthenaPDF
Update application code and configuration for Gotenberg’s different API.
On Wodby
How Gotenberg runs on Wodby
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
POSTrequests to a route per conversion type, for example/forms/chromium/convert/url,/forms/chromium/convert/html(with anindex.htmlfile) 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/healthanswers200with the status of the conversion engines.GET http://<app service name>:3000/versionreturns 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
Versions
Source repository
Public Helm chart
Ports and protocols
Labels
Stacks
Use it inside ready-made stacks or your own
Runtime wiring
Reuse connectivity, storage, and runtime defaults
Endpoints
Technical domains