# 12-Nov-2026 — copy S3-only to unique London buckets and run content migration on the worker [#231](https://github.com/Ramblers-GB/ngx-ramblers/issues/231)

## [build 1078](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/43126913816) — [commit 7b16411](https://github.com/Ramblers-GB/ngx-ramblers/commit/7b16411486dcccca3a36020447f1d162ba8cb82f)

_____

## What's new

- Environment Migration can copy S3 on its own, without touching MongoDB. Use that for the London bucket move: validate, copy, then rotate when the destination objects look right.
- Destination buckets are unique per environment and region (the name includes `eu-west-2`), so two groups no longer fight over the same bucket name in the Ramblers NGX account.
- New London buckets are public for `GET` on walk images, site content, committee files, banners, logos and similar. GPX routes, member bulk-load files, inbox attachments and other private prefixes stay closed; the app still serves those files to people who are allowed to see them.
- Uploads no longer send an object ACL, which London buckets reject. Rotate leaves existing destination keys in place, checks the new key can see the bucket, then switches Fly.
- A failed S3 copy shows as a danger alert on the latest result, not a wiped heading. S3-only results hide the Mongo collection list.
- The environment picker sits above Plan, Latest Result and History, so all three tabs stay on the same group. Clear it to see the whole estate. History Type shows the Mongo and AWS marks (Mongo, S3, or both). Started is `11 Nov 2026 23:23`.
- Content Migration runs on the integration worker with the site's AWS and Mongo credentials, so an import after rotate writes to the new bucket instead of the process that served the admin page. The screen sends an administrator token; downloads only from public HTTP or HTTPS hosts, using the same pinned DNS lookup as site fetch.
- Event Gallery `image.php?file=` imports keep the real filename (for example a WhatsApp `.jpg`) instead of becoming a `.bin`.
- Destroy confirms and deletes the bucket named in the platform environment record, so an existing unsuffixed bucket is not left behind.