swarm-ui: package option moves to deploy.swarm-controller.ui.package
The swarm UI has no switch of its own since it runs wherever the controller runs; its package option follows it under deploy.swarm-controller.ui. deploy.swarm-ui.package and swarm.ui.package stay as renames and warn at evaluation. The flake's default, the vhost root and the module-eval stub use the new path.
This commit is contained in:
parent
8c0a552792
commit
1302288474
6 changed files with 37 additions and 12 deletions
|
|
@ -402,6 +402,10 @@ the UI is a view onto the controller's state and reaches it over that
|
|||
daemon's socket, so the host that runs the controller is the host that
|
||||
can serve the UI. A hive that merely _uses_ a swarm has nothing to serve.
|
||||
|
||||
The UI build is `deploy.swarm-controller.ui.package` (defaulted from this
|
||||
flake's `swarm-ui` package). The older `deploy.swarm-ui.package` and
|
||||
`swarm.ui.package` still work and warn at evaluation.
|
||||
|
||||
The UI answers on `services.hyperhive.swarm.domain` and nothing else. It
|
||||
shares that name with the swarm-controller it fronts — one service to a
|
||||
reader and to a certificate — so there is no separate option to pin.
|
||||
|
|
|
|||
Loading…
Reference in a new issue