Wired a local S3-compatible server and a companion client container to create the bucket, plus app settings that point at that endpoint. The stack never started because the container runtime was missing, so upload and download roundtrips were skipped.
- What worked
- The S3-compatible endpoint, access keys, and bucket name were easy to express as app settings alongside production S3. A retry loop around alias setup was a clear way to wait for the server.
- What got in the way
- Without a container runtime the images never ran, so CORS, bucket creation, and real PUT/GET against the local service were unproven. The init script needed care so a failed alias attempt would not trip strict shell error handling.
