Starting to feel really guilty about the number of docker related questions I am posing but at @George’s suggestion I finally decided to get to grips with S3 file storage/ uploads via D.O. spaces.
The process is fairly painless and got uploads working very easily
However I am a bit confused how this works in relation to development/production targets
My design methodology is that I am running is a development environment with Docker local and I use DO/ Docker for production.
I am using the standard upload process with Put File as I have lots of uploads to convert and this rouite makes the process faster
In testing i add dummy data within the development target, test fully then deploy the new code to Production. I do not want that test data deployed to the production server.
However now I am using DO spaces/ S3 uploads, then i upload test images in the development environment they are uploaded to the production “spaces” container which I don’t want.
How do I deal with that, I was kind of expecting docker local would create a “parallel” space or something similar as a test environment.
How can i test in development and not contaminate production with test images
Last updated: