tanshu
be53cec757
The playbook is meant to be usable on its own, on any host, the way every other one here is: the first run creates the container, and every run after that converges it. It had picked up a migration shape instead -- a readme that assumed a webroot copied in from monoco, a warning that nagged when config.php was missing, and, worse, readiness gates that only passed for an instance that was already installed. That last one was a real bug for the intended use. On a host with no webroot, the image initialises the code, writes no config.php because it has no admin credentials to install with, and serves the setup wizard -- so `occ status` never reports installed: true, and the play would have spent its whole retry budget and then failed on a first run that was going exactly as designed. What replaces it: - The readiness gate is Apache answering status.php inside the container, which is Nextcloud's own endpoint and reports `installed` either way. It is the one thing `is-active` cannot tell us, and it passes for a wizard that has not been completed. - config.php's presence then decides the report: wait for maintenance mode to clear and print `occ status` for an instance, or say what is left for a human to do for a fresh one -- and succeed. The two optional credentials in vars/default.yml install unattended instead, in which case the same endpoints come back installed and the wizard note never appears. - The app creates its own database. Postgres is a shared unit with one default database and nothing else in this repo knows this app's database name, so a fresh cluster previously reached the installer and failed on "database nextcloud does not exist". It is a lookup and a `createdb`, a no-op afterwards, and it fails with the instruction to run postgres/playbook.yml if the cluster is not there rather than with a bare psql error. - Updates. An update in a Quadlet deployment is "pull, then recreate": the unit names a tag, `podman run` reuses the local image, and nothing fetches a newer one. The role pulls on every run and compares the image ID either side, so an unchanged tag is not a change and a running site is not restarted for nothing. - Handlers are flushed before verification, so a queued recreate -- new image, changed unit, changed environment -- happens before the checks rather than after them, and the checks describe what will keep running. Removed: the entire monoco migration section and its copy commands, the config.php warning that existed only to serve it, the host-specific notes, and the narrative comments about this play's first runs. References to the audit and migration planning docs go with them; the ownership reasoning is stated inline, since it does not depend on where an instance came from. `hosts:` is now the only host-specific thing in the directory. The readme is rewritten around the two paths it now has -- "First run" and "Updates" -- with the deploy order, the session-file trap and the debugging commands kept.
30 lines
1.5 KiB
YAML
30 lines
1.5 KiB
YAML
---
|
|
# Attach this app's network to the shared Valkey unit.
|
|
#
|
|
# Valkey knows nothing about its clients, exactly like Caddy and Postgres: a
|
|
# service joins by dropping 50-nextcloud.conf and the shared
|
|
# 10-network-aliases.conf next to valkey.container. The canonical way to do that
|
|
# is the shared include below — it writes the same bytes every service writes,
|
|
# asserts that nextcloud.network already exists, and notifies the "Restart
|
|
# Valkey" handler defined in this role.
|
|
#
|
|
# `redis` is the alias the app connects to, not the container name: REDIS_HOST is
|
|
# what the image writes the PHP session handler from, and what this play puts in
|
|
# config.php's Redis configuration on an unattended install. Renaming it would
|
|
# mean editing a live instance's configuration for nothing.
|
|
|
|
- name: Attach Nextcloud to Valkey
|
|
ansible.builtin.include_tasks: "{{ playbook_dir }}/../valkey/roles/attach/tasks/main.yaml"
|
|
|
|
# On a first attach the drop-in is new, so Valkey has to be recreated to join
|
|
# nextcloud_net — and that restart is a *handler*, which by default runs at the
|
|
# end of the play, after the nextcloud role has already started the app. The app
|
|
# would then come up before `redis` resolves; with `memcache.locking` on Redis it
|
|
# would fail on the first write rather than at startup, which is a worse failure
|
|
# to debug.
|
|
#
|
|
# Flushing applies the new drop-in before the app starts. On later runs the
|
|
# drop-in is unchanged, nothing is pending, and this is a no-op.
|
|
- name: Apply the Valkey network change before starting Nextcloud
|
|
ansible.builtin.meta: flush_handlers
|