How to do binary attachments from server side through gateway to couch-base lite?

[priya.rajagopal]

@feihtthief

Now I need to attach images to go with those documents, but I’m getting stuck. There is no way (that I could find) in the Server SDK to create attachments on documents.

That’s right. There isn’t an SDK API that allows you to directly add attachments to documents. You have the option of embedding it as base64 encoded field associated with document or just uploading the binary blob as a document . FYI - related blog. The recommended approach is to store the binary data is an external store and reference it from the database instead of storing it in line - this is especially true for large attachments.

@feihtthief

That created the documents, but none of those documents seem to appear on the sync gateway. I’m not sure if this is because there are no channels in the document, or if it is something else.

OK. So looks like you used out one of the alternate approaches mentioned above. If the document is added to the CB bucket but isn’t getting processed by SGW, then check your import function in SGW config file.

In fact, please share your SGW config file.

@feihtthief

My next approach was to try to create the documents via the Sync Gateway Rest API and then create attachments for them. Creating the documents worked OK, but the attachments refused to create with a response of {“error”:“Forbidden”,“reason”:“forbidden”}.

Are you providing the right credentials and is there anything in your SGW config file sync function that may be preventing this upload ? Because you should be able to create a document and PUT an attachment .
Please share the exact request that you are using for creating the attachment via the SGW API.

@feihtthief

On a side note: If I try to PUT a document that already exists I keep getting a response of {“error”:“conflict”,“reason”:“Document exists”}, which strikes me as odd given that I understand a PUT to mean “Create or update document” from the documentation

You have to provide the right revision Id of the document that you trying to update via the “rev” parameter.