Lucas RayanandClaude Opus 5
13fd2a9cee
The deployment failed on the migrate service. Coolify rewrites a relative bind mount to a path under its own application directory, and when that resolves to an empty directory golang-migrate finds no migrations and exits 1 - with nothing useful in the deployment log to say why. A deployment that pulls its images has no business also depending on files being at a particular path on the host. Both mounts are now baked into images built from the repository root: migrations - the schema, so migrate always has it rspamd - actions.conf and ratelimit.conf The Rspamd one mattered for a quieter reason: Rspamd starts happily with an empty local.d, so a mount that resolved to nothing would have left the rate limits and score thresholds unapplied. The defence would have looked configured and done nothing. Both images join the CI and release matrices, building from the root context. Verified by building them, checking their contents, and bringing the whole stack up - Rspamd reports its nine rate directives loaded from the image. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
12 lines
413 B
Docker
12 lines
413 B
Docker
# Rspamd with its configuration baked in.
|
|
#
|
|
# The configuration used to arrive through a bind mount. Rspamd starts happily
|
|
# without it, so a mount that resolved to an empty directory would leave the
|
|
# rate limits and score thresholds silently unapplied - the defence would look
|
|
# configured and do nothing.
|
|
#
|
|
# Build context is the repository root.
|
|
FROM rspamd/rspamd:3.9
|
|
|
|
COPY config/rspamd /etc/rspamd/local.d
|