This repository is the index of Wodby-managed service repositories for Wodby 2.0.
Services are reusable definitions for application runtimes, databases, search engines, infrastructure components, and integrations.
Application services are assembled into stacks and deployed as part of user applications. Kubernetes system services are different: Wodby installs and manages them as cluster infrastructure when required by the cluster provider and configuration. They are not user-deployable catalog components.
- Service catalog: https://wodby.com/services
- Service docs: https://wodby.com/docs/2.0/services/
- Service template reference: https://wodby.com/docs/2.0/services/template/
- Service boilerplate: https://github.com/wodby/service
Wodby-maintained images use revision tags such as 11.4-r0. Service option
versions continue to identify the application version; each option's tag
selects a published image revision. The updater preserves variants such as
PostGIS and checks that revision tags exist in both the image registry and Git.
Service releases and Helm chart versions continue to use semantic versions.
Each option also pins its image with digest, the multi-platform index digest
of the image its tag selects (and devDigest for devTag). Deployments use
repository:tag@digest, so clusters run exactly the pinned build. The updater
pins unpinned options and keeps digests in step with tag updates. When a
third-party tag starts pointing to a new build, the updater releases a patch
whose notes describe the rebuild: version variables from the image
configuration and the operating system packages that changed. Wodby revision
tags are never rebuilt, so a new digest for one is reported for review instead.
Options whose tag selects more than one image, such as a service whose
containers share the option tag, are not pinned.
The Service Update workflow checks service repositories daily and after each
push to master, then emails a report of available updates. It releases
planned updates only when the SERVICE_AUTO_RELEASE repository variable is
true or a manual run enables release. A release commits the updates to
the service repository and pushes a new patch tag.
Release notes lead with what changed in the images. For a Wodby image revision
update, the updater reads the image's release note for every revision in the
update. A note that only records a new base image, such as
Base image wodby/alpine: 3.23-r17 -> 3.23-r18, is followed into the base
image's notes, recursively. Bullets and notes that name only other version lines
(Alpine 3.24 for an image on Alpine 3.23) or exclude the image are left out.
When no note applies to a version, the notes compare the two images instead and
list the version and package changes, or say there were none.
A service built on another one (from) lists, under Base service changes,
the changes of every base service release it moves past, taken from those
releases' notes, once each and without changes already listed for its images.
Tag, digest, and base service version updates follow as one short line each,
such as (wodby/php image revision updated to r18 except 8.2); a line that
several manifests share names them together.
A new Helm chart major version isn't released automatically, because it can change the chart's values or resources. The updater keeps the service on the newest chart of its current major version and opens one pull request in the service repository with the new major version for review. It doesn't open a second pull request for the same major version, and doesn't reopen one that was closed. After merging such a pull request, tag a release of the service repository; the updater tags only the changes it makes itself.
Repository discovery checks that every active public service-* repository is
listed below. A missing entry fails the workflow so it cannot silently lose
update coverage. External services have no managed software to update.
GitLab and GitLab Runner are planned and released as one batch. Filtering for either service includes both. The updater reads both charts' application versions, keeps their major/minor release line aligned, and verifies the exact Alpine Runner image tag. Patch versions may differ between the two products. It prepares both repositories before publishing either release. Minor and major application upgrades require review of GitLab's upgrade path.
Supabase updates use all eight component images from one published Wodby chart, checked against that chart's exact upstream self-hosted release. The chart, application option, component images, and any Studio bootstrap override advance together. Updates that change the upstream database image, roll back an image, or require upstream manual steps appear as review-only diffs. New upstream releases without a compatible published chart are reported for review; individual components are not advanced independently.
New application release lines are reported for manual review, using upstream tags or published image versions when end-of-life data has no version source. Missing end-of-life dates still require review; the updater does not invent them.
Each repository's branch and release tag are pushed atomically. GitHub cannot publish multiple repositories atomically. If a later batch push fails, the report preserves successful releases; rerun the workflow to plan the remaining updates from the current repository state.
Use the service boilerplate when you want to
create a custom Git-backed service. It includes a valid service.yml, starter
build files, and README guidance.
For a single service repository, put service.yml at the repository root. For a
repository that contains multiple services, add an index.yml with service
directories:
services:
- api
- workerBefore publishing a service for others to use, review:
| Service | Repository |
|---|---|
| Nginx | wodby/service-nginx |
| Nginx Proxy | wodby/service-nginx-proxy |
| Nginx for PHP | wodby/service-php-nginx |
| Nginx for Drupal | wodby/service-drupal-nginx |
| Nginx for WordPress | wodby/service-wordpress-nginx |
| Nginx for Laravel | wodby/service-laravel-nginx |
| Nginx for Matomo | wodby/service-matomo-nginx |
| Nginx for Moodle | wodby/service-moodle-nginx |
| Nginx for Odoo | wodby/service-odoo-nginx |
| Nginx for buildable Moodle | wodby/service-moodle-buildable-nginx |
| Apache HTTPD | wodby/service-httpd |
| Apache HTTPD for PHP | wodby/service-php-httpd |
| Vinyl | wodby/service-vinyl |
| Vinyl for Drupal | wodby/service-drupal-vinyl |
| Vinyl for WordPress | wodby/service-wordpress-vinyl |
| Varnish | wodby/service-varnish |
| Varnish for Drupal | wodby/service-drupal-varnish |
| Varnish for WordPress | wodby/service-wordpress-varnish |
| Service | Repository |
|---|---|
| Tailscale | wodby/service-tailscale |
| NetBird | wodby/service-netbird |
| 3X UI | wodby/service-3xui |
| FRP Server | wodby/service-frps |
| RustDesk Server | wodby/service-rustdesk |
| Service | Repository |
|---|---|
| GitLab Community Edition | wodby/service-gitlab |
| GitLab Runner | wodby/service-gitlab-runner |
| Gitea | wodby/service-gitea |
| Forgejo | wodby/service-forgejo |
| Supabase | wodby/service-supabase |
| Service | Repository |
|---|---|
| MariaDB | wodby/service-mariadb |
| MongoDB | wodby/service-mongodb |
| MySQL | wodby/service-mysql |
| PostgreSQL | wodby/service-postgres |
| Supabase PostgreSQL | wodby/service-supabase-postgres |
| PostGIS | wodby/service-postgis |
| Cloud MySQL | wodby/service-cloud-mysql |
| Cloud MariaDB | wodby/service-cloud-mariadb |
| Cloud PostgreSQL | wodby/service-cloud-postgres |
| Valkey | wodby/service-valkey |
| Redis | wodby/service-redis |
| Memcached | wodby/service-memcached |
| RabbitMQ | wodby/service-rabbitmq |
| Distribution Registry | wodby/service-distribution |
| Solr | wodby/service-solr |
| Elasticsearch | wodby/service-elasticsearch |
| OpenSearch | wodby/service-opensearch |
| Meilisearch | wodby/service-meilisearch |
| ClickHouse | wodby/service-clickhouse |
| Apache Kafka | wodby/service-kafka |
| Apache Spark | wodby/service-spark |
| Apache Airflow | wodby/service-airflow |
| ZooKeeper | wodby/service-zookeeper |
| Gotenberg | wodby/service-gotenberg |
| Service | Repository |
|---|---|
| authentik | wodby/service-authentik |
| Keycloak | wodby/service-keycloak |
| Keycloak (buildable) | wodby/service-keycloak-buildable |
| Service | Repository |
|---|---|
| Adminer | wodby/service-adminer |
| Mongoku | wodby/service-mongoku |
| phpMyAdmin | wodby/service-phpmyadmin |
| pgAdmin | wodby/service-pgadmin |
| Service | Repository |
|---|---|
| Prometheus | wodby/service-prometheus |
| Grafana | wodby/service-grafana |
| Kibana | wodby/service-kibana |
| OpenSearch Dashboards | wodby/service-opensearch-dashboards |
| Grafana Loki | wodby/service-loki |
| VictoriaMetrics | wodby/service-victoria-metrics |
| Grafana Tempo | wodby/service-tempo |
| OpenTelemetry Collector | wodby/service-opentelemetry-collector |
| Service | Repository |
|---|---|
| Mailpit | wodby/service-mailpit |
| OpenSMTPD | wodby/service-opensmtpd |
These services back Wodby-managed Kubernetes infrastructure. They are installed through system stacks during cluster provisioning and are not intended for user-created application stacks.
| Service | Repository |
|---|---|
| Monitoring | wodby/service-monitoring |
| Metrics Server | wodby/service-metrics-server |
| Node Exporter | wodby/service-node-exporter |
| Kube State Metrics | wodby/service-kube-state-metrics |
| AWS LB Controller | wodby/service-aws-lb-controller |
| Envoy Gateway | wodby/service-envoy-gateway |
| Ingress Nginx | wodby/service-ingress-nginx |
| FRPC | wodby/service-frpc |
| Service | Repository |
|---|---|
| NFS Provisioner | wodby/service-nfs-provisioner |
| Service | Repository |
|---|---|
| Open WebUI | wodby/service-open-webui |
| OpenClaw | wodby/service-openclaw |
| T3 Code | wodby/service-t3code |
| vLLM (preview) | wodby/service-vllm |