camallen
commented
9 years ago @alianos- so we store our subjects on s3 for distribution. Sounds like you have your own subject hosting service so you don't need to leverage this but those URL's will be stored in the subject locations. It sounds like your front end uses the metadata fields to link the coords and the image, e.g.
{ "subjects": [
{
"id": "1",
"locations": [
{
"image/jpeg": "http://s3.amazonaws.com/subjects/1.png"
}
],
"metadata": {
"file_location": "http://WMS_SERVER_URL/file_1.image_ext",
"coords": [ 1, 1 ]
},
} ]
}If this is the case then it's up to your front end to understand the custom metadata hash URL format. To avoid this error you can just edit your aws.yml config for the development and the production env (if / when you run in production mode), make it look like the test env if you want but those values will propogate to your 'locations' object (but you'll ignore them anyway).
As our API is not at version 1 yet (it's getting there). We've got work planned to use different subject storage locations via #425. This will be by configurable and you should be able to specify location URL's if you've got them hosted elsewhere.
alianos-
So I am trying to add subjects. I use "text/plain" because really we only store coordinates and we will retrieve the images from a WMS server. (Btw I am storing the coordinates in the metadata, any better ideas?)
I get the following error in the response, but then when I list subjects they have been are added like nothing happened.
AWS::Errors::MissingCredentialsError in Api::V1::SubjectsController#create(in detail)