Base64 | Base64 encoding and decoding | Base64 library

Try this:

To update existing image you should use html.Img(...) instead of html.Div(..., children=[]) in app.layout, and update component_property='src' instead of component_property='children'

Many tools can save image/file in file-like object created in memory with io.BytesIO()

Example for matplotlib

Per the documentation for Canvg.from, you need to pass it your drawing context, not the canvas itself. So change this line:

CloudFormation (CFN) is not going to take your chaklader.pem and create a pair key in AWS. You have to do it before hand yourself. And you can't use CFN for that as it is not supported, unless you will program such a logic yourself using custom resource.

The easiest way is to create or import the key "manually" using AWS Console, SDK or CLI. Then you can reference its name in your template.

I try to avoid text only answers; including code is best practice but the question about storing images comes up frequently and it's not really covered in the documentation so I thought it should be addressed at a high level.

Generally speaking, Realm is not a solution for storing blob type data - images, pdf's etc. There are a number of technical reasons for that but most importantly, an image can go well beyond the capacity of a Realm field. Additionally it can significantly impact performance (especially in a sync'ing use case)

If this is a local only app, storing the images on disk in the device and keep a reference to where they are (their path) stored in Realm. That will enable the app to be fast and responsive with a minimal footprint.

If this is a sync'd solution where you want to share images across devices or with other users, there are several cloud based solutions to accommodate image storage and then store a URL to the image in Realm.

One option is part of the MongoDB family of products (which also includes MongoDB Realm) called GridFS. Another option is a solid product we've leveraged for years is called Firebase Cloud Storage.

Now that I've made those statements, I'll backtrack just a bit and refer you to this article Realm Data and Partitioning Strategy Behind the WildAid O-FISH Mobile Apps which is a fantastic article about implementing Realm in a real-world use application and in particular how to deal with images.

In that article, note they do store the images in Realm for a short time. However, one thing they left out of that (which was revealed in a forum post) is that the images are compressed to ensure they don't go above the Realm field size limit.

I am not totally on board with general use of that technique but it works for that specific use case.

One more note: the image sizes mentioned in the question are pretty small (500 ~~ 800 kb img size) and that's a tiny amount of data which would really not have an impact, so storing them in realm as a data object would work fine. The caveat to that is future expansion; if you decide to later store larger images, it would require a complete re-write of the code; so why not plan for that up front.

With regards to the image analysis resolution, the documentation of ImageAnalysis.Builder.setTargetResolution() states that:

The maximum available resolution that could be selected for an ImageAnalysis is limited to be under 1080p.

So setting a size of 2560x800 won't work as you expect. In return CameraX seems to be selecting the maximum ImageAnalysis resolution that has the same aspect ratio you requested (2560/800 = 1280/400).

EDIT: BETTER WAY

INSTEAD OF EDITING THE STRING IN THE SERVER WE SHOULD ENCODE IN ANDROID THIS WAY

Base64.encodeToString(bytes, Base64.NO_WRAP);

AND GET IT IN THE SERVER THE USUAL WAY WITHOUT EDITING THE STRING

java.util.Base64.getMimeDecoder().decode(yourByteArray);

PREVIOUS WAY:

I just had to edit the String that i was getting in the server by removing the quotes surrounding it with img.substring(1, img.length() - 1) and the \n with img.replace("\\n", "").

The result code in the server is like this:

You get the above error as id is the mandatory parameter in Details function (action) in Employee controller.

Apparently, the solution was to start Kirby using php -S 0.0.0.0:8000 instead of using php -S localhost:8000, and then reaching the API via http://0.0.0.0:8000/api instead of http://localhost:8000/api.