Commit Graph
3258 Commits
Author SHA1 Message Date
Jose Diaz-Gonzalez fa0f031560 Merge pull request #9157 from dokku/dependabot/pip/docs/_build/markdown-gte-3.11.1-and-lt-3.12
chore(deps): update markdown requirement from <3.12,>=3.11 to >=3.11.1,<3.12 in /docs/_build
2026-10-21 12:59:38 -04:00
Jose Diaz-Gonzalez dfcaa08a6c Merge pull request #9156 from dokku/dependabot/pip/docs/_build/pymdown-extensions-12.3
chore(deps): bump pymdown-extensions from 12.2 to 12.3 in /docs/_build
2026-10-20 10:39:55 -04:00
dependabot[bot] 81012f0fb5 chore(deps): bump python in /docs/_build
Bumps python from 3.15.0rc3-alpine to 3.16.0a1-alpine.

---
updated-dependencies:
- dependency-name: python
  dependency-version: 3.16.0a1-alpine
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-20 13:52:47 +00:00
dependabot[bot] e98b04d48f chore(deps): update markdown requirement in /docs/_build
Updates the requirements on [markdown](https://github.com/Python-Markdown/markdown) to permit the latest version.
- [Release notes](https://github.com/Python-Markdown/markdown/releases)
- [Changelog](https://github.com/Python-Markdown/markdown/blob/master/docs/changelog.md)
- [Commits](https://github.com/Python-Markdown/markdown/compare/3.11.0...3.11.1)

---
updated-dependencies:
- dependency-name: markdown
  dependency-version: 3.11.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-19 14:00:11 +00:00
dependabot[bot] 149c63d74d chore(deps): bump pymdown-extensions from 12.2 to 12.3 in /docs/_build
Bumps [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) from 12.2 to 12.3.
- [Release notes](https://github.com/facelessuser/pymdown-extensions/releases)
- [Commits](https://github.com/facelessuser/pymdown-extensions/compare/12.2...12.3)

---
updated-dependencies:
- dependency-name: pymdown-extensions
  dependency-version: '12.3'
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-19 14:00:04 +00:00
Jose Diaz-Gonzalez cbde55a4a0 fix: respect DOKKU_LIB_HOST_ROOT for storage bind mounts
When Dokku runs in Docker with a shared socket, create/chown still use
DOKKU_LIB_ROOT inside the container, but Docker -v flags for storage:exec
and deploy must use DOKKU_LIB_HOST_ROOT so the daemon mounts the host data
volume instead of the real host's /var/lib/dokku.

Closes #9126.
2026-10-16 11:52:01 -04:00
dependabot[bot] bf999dc536 chore(deps): bump soupsieve from 2.10 to 3.0.3 in /docs/_build
Bumps [soupsieve](https://github.com/facelessuser/soupsieve) from 2.10 to 3.0.3.
- [Release notes](https://github.com/facelessuser/soupsieve/releases)
- [Commits](https://github.com/facelessuser/soupsieve/compare/2.10...3.0.3)

---
updated-dependencies:
- dependency-name: soupsieve
  dependency-version: 3.0.3
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-15 13:53:32 +00:00
dependabot[bot] 92cf98e87d chore(deps): bump pymdown-extensions from 12.1 to 12.2 in /docs/_build
Bumps [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) from 12.1 to 12.2.
- [Release notes](https://github.com/facelessuser/pymdown-extensions/releases)
- [Commits](https://github.com/facelessuser/pymdown-extensions/compare/12.1...12.2)

---
updated-dependencies:
- dependency-name: pymdown-extensions
  dependency-version: '12.2'
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-13 16:05:17 +00:00
Jose Diaz-Gonzalez 80409c7c59 Merge pull request #9131 from dokku/fix-source-image-on-failed-deploy
Keep the git source-image property in sync and harden the deploy lock
2026-10-12 11:53:20 -04:00
Satvik Mishra be73a60fa0 docs: fix broken internal anchors and links 2026-10-12 00:36:59 +05:30
Jose Diaz-Gonzalez 7955e8ee06 fix: keep the git source-image property in sync with failed deploys
The source-image property was written before the deploy lock was taken
and was not restored when a deploy failed, so after a rejected
git:from-image or git:load-image it named an image that was not
deployed, and later builds extracted app.json, Procfile, and CHECKS
from it. Deploys from other sources also built while the old image was
still set.

Entry points now pass the desired value via DOKKU_GIT_SOURCE_IMAGE and
git_receive_app applies it while holding the deploy lock, restoring the
previous value on failure. git:sync clears the property under the lock
when it fetches new code.

Closes #9117
2026-10-11 05:08:32 -04:00
dependabot[bot] d0bfcc5ede chore(deps): bump python in /docs/_build
Bumps python from 3.15.0rc2-alpine to 3.15.0rc3-alpine.

---
updated-dependencies:
- dependency-name: python
  dependency-version: 3.15.0rc3-alpine
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-09 13:53:21 +00:00
fmtappendf d82d0088a1 chore: fix some typos in comment
Signed-off-by: fmtappendf <fmtappendf@gmail.com>
2026-10-08 16:20:11 +08:00
Jose Diaz-Gonzalez 8f78c37bfd Merge pull request #9116 from libredb/add-libredb-studio-plugin
Add LibreDB Studio plugin to community plugin list
2026-10-08 01:27:44 -04:00
dependabot[bot] f5b903c5bd chore(deps): bump zipp from 4.1.0 to 4.1.1 in /docs/_build
Bumps [zipp](https://github.com/jaraco/zipp) from 4.1.0 to 4.1.1.
- [Release notes](https://github.com/jaraco/zipp/releases)
- [Changelog](https://github.com/jaraco/zipp/blob/main/NEWS.rst)
- [Commits](https://github.com/jaraco/zipp/compare/v4.1.0...v4.1.1)

---
updated-dependencies:
- dependency-name: zipp
  dependency-version: 4.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-07 13:54:00 +00:00
cevheri b5b69ba8f4 Add LibreDB Studio plugin to community plugin list 2026-10-06 22:38:31 +03:00
Jose Diaz-Gonzalez e2f4a00a3d Merge pull request #9104 from dokku/cron-entries-mailto
Allow cron-entries to set a per-entry MAILTO
2026-10-06 14:50:42 -04:00
dependabot[bot] e78d24ff50 chore(deps): bump markupsafe from 3.0.3 to 3.0.4 in /docs/_build
Bumps [markupsafe](https://github.com/pallets/markupsafe) from 3.0.3 to 3.0.4.
- [Release notes](https://github.com/pallets/markupsafe/releases)
- [Changelog](https://github.com/pallets/markupsafe/blob/main/CHANGES.rst)
- [Commits](https://github.com/pallets/markupsafe/compare/3.0.3...3.0.4)

---
updated-dependencies:
- dependency-name: markupsafe
  dependency-version: 3.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-10-06 14:24:05 +00:00
Jose Diaz-Gonzalez b158f482ef fix: reset MAILTO after a cron entry that sets its own
A task with its own `MAILTO` is now written in place, followed by a line resetting `MAILTO` to the global value, or to the `dokku` user when none is set, rather than grouped at the end of the crontab, so no other task is mailed to its recipient whatever order the tasks are written in.
2026-09-30 17:47:27 -04:00
Jose Diaz-Gonzalez f91b1f7fc7 feat: allow cron-entries to set a per-entry MAILTO
The `cron-entries` trigger is now passed `json` as a second argument, and plugins may print each task as a json object on its own line. A task that sets a `mailto` is written to the crontab under a `MAILTO` of its own, and its output is mailed to that address as well as appended to its log file, so plugins such as the datastore plugins can have the output of a specific scheduled task mailed to a specific person.
2026-09-30 17:01:25 -04:00
Jose Diaz-Gonzalez 33b70abbf1 Merge pull request #9102 from dokku/missing-nginx-vhosts
fix: allow enabling nginx-vhosts when skipped at install
2026-09-29 23:59:59 -04:00
Jose Diaz-Gonzalez cc0c870bfd Merge pull request #9090 from dokku/dependabot/pip/docs/_build/soupsieve-2.10
chore(deps): bump soupsieve from 2.9.2 to 2.10 in /docs/_build
2026-09-29 12:32:49 -04:00
Jose Diaz-Gonzalez 2a9aa6246f Merge pull request #9089 from dokku/dependabot/pip/docs/_build/pymdown-extensions-12.1
chore(deps): bump pymdown-extensions from 12.0.1 to 12.1 in /docs/_build
2026-09-29 12:27:09 -04:00
Jose Diaz-Gonzalez 46776fa87c fix: allow enabling nginx-vhosts when skipped at install
Installing with the `dokku/nginx_enable` debconf option set to `false` left the nginx-vhosts plugin disabled with no way to turn it back on, as `dokku plugin:enable nginx-vhosts` reported that the plugin does not exist. The plugin can now be enabled after installation, and the debconf documentation explains the option's effect and how to reverse it.
2026-09-29 12:11:17 -04:00
dependabot[bot] 4d32c73847 chore(deps): bump soupsieve from 2.9.2 to 2.10 in /docs/_build
Bumps [soupsieve](https://github.com/facelessuser/soupsieve) from 2.9.2 to 2.10.
- [Release notes](https://github.com/facelessuser/soupsieve/releases)
- [Commits](https://github.com/facelessuser/soupsieve/compare/2.9.2...2.10)

---
updated-dependencies:
- dependency-name: soupsieve
  dependency-version: '2.10'
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-09-28 14:38:55 +00:00
dependabot[bot] 4bc48844ef chore(deps): bump pymdown-extensions from 12.0.1 to 12.1 in /docs/_build
Bumps [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) from 12.0.1 to 12.1.
- [Release notes](https://github.com/facelessuser/pymdown-extensions/releases)
- [Commits](https://github.com/facelessuser/pymdown-extensions/compare/12.0.1...12.1)

---
updated-dependencies:
- dependency-name: pymdown-extensions
  dependency-version: '12.1'
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-09-28 14:38:49 +00:00
dependabot[bot] 2ffb08db73 chore(deps): update markdown requirement in /docs/_build
Updates the requirements on [markdown](https://github.com/Python-Markdown/markdown) to permit the latest version.
- [Release notes](https://github.com/Python-Markdown/markdown/releases)
- [Changelog](https://github.com/Python-Markdown/markdown/blob/master/docs/changelog.md)
- [Commits](https://github.com/Python-Markdown/markdown/compare/3.10.3...3.11.0)

---
updated-dependencies:
- dependency-name: markdown
  dependency-version: '3.11'
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-09-28 14:38:44 +00:00
Dokku Bot 540a146757 Release 0.38.31
# History

## 0.38.31

Install/update via the bootstrap script:

```shell
wget -NP . https://dokku.com/install/v0.38.31/bootstrap.sh
sudo DOKKU_TAG=v0.38.31 bash bootstrap.sh
```

### Bug Fixes

- #9084: @josegonzalez Report stored node-sysctls images globally
- #9082: @josegonzalez Verify existing apps in git commands
- #9081: @josegonzalez Validate run:logs arguments
- #9080: @josegonzalez Check app directory when creating a new app
- #9079: @josegonzalez Validate app name in app-scoped commands
- #9077: @josegonzalez Respect quoting in procfile commands and remove support for bare shell operators
- #9076: @josegonzalez Validate app.json healthcheck path and scheme

### Dependencies

- #9078: @dependabot[bot] chore(deps): bump pyparsing from 3.3.2 to 3.3.3 in /docs/_build
2026-09-26 07:10:44 +00:00
Jose Diaz-Gonzalez 7a0404a2ec fix: report stored node-sysctls images globally
The `--scheduler-k3s-global-node-sysctls-image` and `--scheduler-k3s-global-node-sysctls-pause-image` report flags returned the built-in default when nothing was stored, so an unset image could not be told apart from one set to the default. They now report the stored value like every other global flag, and new `--scheduler-k3s-computed-node-sysctls-image` and `--scheduler-k3s-computed-node-sysctls-pause-image` flags report the image that is actually used.
2026-09-26 01:14:15 -04:00
Jose Diaz-Gonzalez 114c6115b9 Merge pull request #9078 from dokku/dependabot/pip/docs/_build/pyparsing-3.3.3
chore(deps): bump pyparsing from 3.3.2 to 3.3.3 in /docs/_build
2026-09-24 16:53:14 -04:00
dependabot[bot] dd5eff55d6 chore(deps): bump pyparsing from 3.3.2 to 3.3.3 in /docs/_build
Bumps [pyparsing](https://github.com/pyparsing/pyparsing) from 3.3.2 to 3.3.3.
- [Release notes](https://github.com/pyparsing/pyparsing/releases)
- [Changelog](https://github.com/pyparsing/pyparsing/blob/master/CHANGES)
- [Commits](https://github.com/pyparsing/pyparsing/compare/3.3.2...3.3.3)

---
updated-dependencies:
- dependency-name: pyparsing
  dependency-version: 3.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-09-24 13:53:26 +00:00
Jose Diaz-Gonzalez 1f8a814047 fix: respect quoting in procfile commands
Procfile commands for the `docker-local` scheduler were split differently on deploy and on `dokku run`. Deploys failed on escaped quotes, and `dokku run` ignored quotes entirely. Both now split commands using shell quoting rules, and commands containing bare shell operators fail with a clear error, matching the `k3s` scheduler.
2026-09-24 01:24:27 -04:00
Jose Diaz-Gonzalez db42d0a039 fix: validate app.json healthcheck path and scheme 2026-09-23 23:12:58 -04:00
Dokku Bot f57b3455c1 Release 0.38.30
# History

## 0.38.30

Install/update via the bootstrap script:

```shell
wget -NP . https://dokku.com/install/v0.38.30/bootstrap.sh
sudo DOKKU_TAG=v0.38.30 bash bootstrap.sh
```

### New Features

- #9074: @josegonzalez Allow storage:mount --replace to vary fields per mount
- #9075: @josegonzalez Report each node-sysctls scope's stored map

### Tests

- #9071: @dependabot[bot] chore(deps): bump google.golang.org/grpc from 1.83.2 to 1.84.0 in /tests/apps/gogrpc
2026-09-23 08:03:32 +00:00
Jose Diaz-Gonzalez 5dd9111d44 Merge pull request #9074 from dokku/9072-allow-storage-mount-replace-to-vary-mount-time-fields-per-mount
Allow storage:mount --replace to vary fields per mount
2026-09-23 04:02:02 -04:00
Jose Diaz-Gonzalez 551c6b1c43 feat: report each node-sysctls scope's stored map
`scheduler-k3s:node-sysctls:report` renders each scope's resolved set, so a profile's entry carries every globally-set sysctl underneath its own and there is no way to read back the map the profile itself stores. Since `node-sysctls:set --replace --profile` and `node-sysctls:clear --profile` write only that map, a tool converging a profile against a declared map sees permanent drift. The new `--stored` flag reports the map each scope owns, and `--global` and `--profile` narrow the report to a single scope. The default output is unchanged.
2026-09-23 02:09:33 -04:00
Jose Diaz-Gonzalez bf26539949 feat: allow storage:mount --replace to vary fields per mount
`storage:mount --replace` writes one process type's whole attachment set in a single call, but only part of an attachment could vary between the mounts in that call: each mount carried its own `ro` and Docker mount options while `--phase`, `--volume-subpath` and `--volume-chown` were fixed for the whole call, so an app whose mounts differ only in subpath still needed one call per mount, which is the non-atomic convergence `--replace` exists to remove. Each mount's option list now also carries `phase=`, `volume-subpath=` and `volume-chown=` tokens alongside `ro`, its new opposite `rw` and the Docker options it already passed through, and so that each attribute has exactly one spelling the five matching flags are now rejected with `--replace` - one of which, `--volume-options`, was previously accepted and silently dropped. `--process-type` still scopes the whole call, since it selects which mounts the call is authoritative over rather than describing any one of them. Every mount is parsed and validated before anything is written, so a rejected token leaves the stored mounts untouched. The documentation added for `--replace` was also marked as new in 0.38.28 in four places, but it shipped in 0.38.29.
2026-09-23 01:10:49 -04:00
Dokku Bot 55535dd2fc Release 0.38.29
# History

## 0.38.29

Install/update via the bootstrap script:

```shell
wget -NP . https://dokku.com/install/v0.38.29/bootstrap.sh
sudo DOKKU_TAG=v0.38.29 bash bootstrap.sh
```

### Bug Fixes

- #9060: @josegonzalez Preserve global flags when sudo is sudo-rs
- #9055: @josegonzalez Validate nginx templates as the running nginx user
- #9054: @josegonzalez Honor the pinned chart version when upgrading
- #9049: @josegonzalez Report config write failures instead of exiting 0
- #9050: @josegonzalez Reject negative process counts when scaling

### New Features

- #9058: @josegonzalez Add a whole-set form for an app's storage mounts
- #9057: @josegonzalez Add a way to read back registry login state
- #9051: @josegonzalez Add a whole-set form for scheduler-k3s metadata

### Documentation

- #9070: @s01ipsist Document Ubuntu 26.04 as a supported installation target

### Tests

- #9062: @josegonzalez Pass force to the datastore command that owns it
- #9061: @josegonzalez Call the datastore create command the way it is documented

### Dependencies

- #9064: @dependabot[bot] chore: group gomod dependabot updates across all plugins
- #9066: @dependabot[bot] chore(deps): bump github.com/onsi/gomega from 1.43.0 to 1.43.1 in /plugins/buildpacks
- #9067: @dependabot[bot] chore(deps): bump github.com/fluxcd/pkg/kustomize from 1.40.0 to 1.41.0 in /plugins/scheduler-k3s
- #9063: @dependabot[bot] chore(deps): bump pymdown-extensions from 12.0 to 12.0.1 in /docs/_build
- #9068: @dependabot[bot] chore(deps): bump github.com/onsi/gomega from 1.43.0 to 1.43.1 in /plugins/scheduler-k3s
- #9052: @dependabot[bot] chore(deps): bump pymdown-extensions from 11.0.2 to 12.0 in /docs/_build

### Other

- #9069: @josegonzalez Honor storage attachment process types at deploy time
- #9011: @visheshgubrani Propagate command exit code on dokku run
2026-09-22 23:55:12 +00:00
Sam GiffneyandClaude Opus 5.5 02a9f29c36 Document Ubuntu 26.04 as a supported installation target
Ubuntu 26.04 was added to the bootstrap installer's supported versions
in #8791 (released in 0.38.28). Update the README, installation
requirements and testing docs to match.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-23 09:50:43 +10:00
Jose Diaz-Gonzalez 867481a642 Merge pull request #9069 from dokku/9059-storage-attachment-process-types-are-recorded-but-not-honored-at-deploy-time
Honor storage attachment process types at deploy time
2026-09-22 15:09:57 -04:00
Jose Diaz-Gonzalez 17cf249f2e fix: fail deploy tasks when a docker-args trigger fails
The ephemeral containers that run `app.json` deploy tasks ignored a failure from the `docker-args-deploy` and `docker-args-process-deploy` triggers, so a plugin refusing to describe the container produced a task that ran without the arguments it had asked for, while the very same failure aborted the deploy moments later on the scheduler's own path. Both are now fatal, which the trigger documentation states. Storage no longer reports a scheduler mismatch for an app deploying with another scheduler, since those triggers are fired for every app whatever its scheduler and a k3s app's volumes are mounted by k3s rather than bound into a container here.
2026-09-21 23:35:28 -04:00
Jose Diaz-Gonzalez b612285392 fix: honor storage attachment process types at deploy time
An attachment's process type was recorded, reported and used to scope `storage:mount --replace` and `storage:unmount --all`, but nothing read it when the volume was actually mounted, so `storage:mount <app> <entry> --container-dir <path> --process-type web` bound the volume into every process rather than only `web`. Both schedulers now scope a mount to the process type it was declared for, and containers that belong to no process type - a `dokku run` one-off, an `app.json` deploy task, a k3s cron job - receive default-scoped mounts only. A container path can now be claimed by a single mount per process type, and `storage:migrate` drains process-scoped `-v` lines out of `docker-options` rather than only the default-scoped ones.
2026-09-21 18:08:42 -04:00
dependabot[bot] eeaeb211f5 chore(deps): bump pymdown-extensions from 12.0 to 12.0.1 in /docs/_build
Bumps [pymdown-extensions](https://github.com/facelessuser/pymdown-extensions) from 12.0 to 12.0.1.
- [Release notes](https://github.com/facelessuser/pymdown-extensions/releases)
- [Commits](https://github.com/facelessuser/pymdown-extensions/compare/12.0...12.0.1)

---
updated-dependencies:
- dependency-name: pymdown-extensions
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-09-21 13:53:54 +00:00
Jose Diaz-Gonzalez 63e4b92a52 fix: forward every environment-overridable dokku variable
`DOKKU_INIT_SYSTEM` reaches the `dokku` user only through the environment while the Docker image is being built, so narrowing the forwarded set left `nginx:reload` taking the systemd branch during `debian/postinst` and blocking on a sudo password prompt until the build timed out. The forwarded set now covers every variable `dokku` honours from the environment, and `DOKKU_PRESERVE_ENV` still carries anything beyond it.
2026-09-20 16:25:34 -04:00
Jose Diaz-Gonzalez 6b1b7bc6f6 fix: preserve global flags when sudo is sudo-rs
`sudo-rs`, the default sudo on Ubuntu 25.10 and later, does not support preserving the entire environment, so `--quiet`, `--trace`, `--force` and `--app` stopped taking effect once `dokku` re-executed itself as the `dokku` user, and a warning was printed on every invocation. Variables outside the set dokku forwards no longer cross that boundary and can be named in `DOKKU_PRESERVE_ENV` instead.
2026-09-20 04:11:15 -04:00
Jose Diaz-Gonzalez 1d0985428a feat: add a whole-set form for an app's storage mounts
The `storage` plugin mounted and unmounted one attachment at a time, so matching an app's mounts to a declared set meant reading `storage:list`, computing the difference in both directions and issuing one `storage:mount` or `storage:unmount` per addition and removal, with a failure partway through leaving the app holding a mixture of the two sets.

A `--replace` flag on `storage:mount` now writes the declared set in a single call, taking `name:container-dir` pairs whose optional third field carries the same mount options the legacy colon form accepts. Every pair is parsed and validated before anything is written, so a rejected pair leaves the stored mounts untouched. The remaining mount-time flags scope the whole call the way `--process-type` already scoped a single mount, which means an omitted `--process-type` replaces the `_default_` scope and leaves mounts scoped to a named process type in place.

An empty pair list is rejected rather than treated as a request to unmount everything, so a generated list that expands to nothing cannot silently drop an app's storage. `storage:unmount --all` handles that case instead, taking an optional `--process-type` filter and treating a scope that matches nothing as a no-op so it stays idempotent.

`storage:unmount` also accepts more than one mount at a time, naming each by entry name or by the colon form, and resolves every argument against the app's attachments before removing any of them.

The help listing now carries one entry per subcommand with its flags inline rather than a row per variant, and the command listing at the top of the storage documentation matches it line for line. Folding those rows together also surfaced `--global` on `storage:report` and `storage:migrate`, neither of which both listings had mentioned.

Finally, `--volume-chown` is now validated on mount, where a typo previously exited zero and wrote a value that only the report ever read.
2026-09-20 01:06:14 -04:00
Jose Diaz-Gonzalez f36512a19d Merge pull request #9055 from dokku/9037-nginx-conf-sigil-pre-validation-chowns-proxy-cache-path-directories-to-nobody-breaking-the-running-nginx-for-the-whole-build
Validate nginx templates as the running nginx user
2026-09-19 21:20:56 -04:00
Jose Diaz-Gonzalez 624eea1959 feat: add registry:auth-status to read back login state
There was no way to ask whether Dokku was already logged in to a registry with a given credential, so tooling converging a declared state onto a server had to re-run `registry:login` on every pass purely to discover that nothing needed to change. The new `registry:auth-status` command compares a supplied credential against the stored one and reports the result through its exit code alone, distinguishing a server with no credential from one whose credential differs, and from one whose secret a docker credential helper or an identity token puts out of reach. An `auth-servers` triad on `registry:report` exposes which servers have credentials without emitting any part of one.
2026-09-19 19:19:57 -04:00
Jose Diaz-Gonzalez a4f791b85d Merge pull request #9054 from dokku/9053-scheduler-k3s-ensure-charts-ignores-the-pinned-chart-version-when-upgrading-an-existing-release
Honor the pinned chart version when upgrading
2026-09-19 10:19:41 -04:00
Jose Diaz-Gonzalez 3423779f0f fix: validate nginx templates as the running nginx user
The wrapper config used to run `nginx -t` against an app's rendered `nginx.conf` declared no `user` directive, so nginx fell back to its compile-time default and chowned every `proxy_cache_path` directory to that user, including directories that already existed. On Debian and Ubuntu that default is `nobody`, so deploying an app shipping a custom `nginx.conf.sigil` took the running server's live cache directory away for the length of the build and turned every request the cache would serve into an HTTP 500, healing only once the deploy's own reload restored the ownership. The wrapper now declares the same `user` as the host's main nginx config, which is also exposed to custom `validate-config` templates as `$.NGINX_USER`.
2026-09-19 10:06:35 -04:00