image-uploads | : sunrise : Effortless Image Uploads | File Upload library

Postman's PHP/curl code generator isn't very good. to upload files in the multipart/form-data-format, use CURLFile.

the code should be

UPDATE:

You really need to learn jquery if you're going to make any of this work. You have many points of possible failure so try to listen to what the error messages tell you. There are couple of ways you can debug your broken JS

throw a debugger in and go in the console to see what your objects are and what functions can be called on them. I'd start here:

You just need do some changes

model:

You should send base64 encoded image data (not file upload) via postman (in case, you are using Base64ImageField)

You can refer this also: Error uploading image using postman in django rest framework

How to send a base64 image in postman

Process of getting encoded image

1. Use Image encoder for image encoding. After image upload, you will have an option of copy image.
2. Copy the data and paste it in and .txt file
3. You will get an string with prefix 'data:image/png;base64,'
4. Remove that prefix from string and paste the whole string in POSTMAN

Your code base is part of Git, you might use Git to deploy that to a webspace. The webspace itself is not in Git. The remote Git repo syncs or copies it's contents to the webspace.

It's not a matter of setting the right .gitignore rules. The files on the webspace can change: When the software rights temp-, log-, cache-files or user-uploads for instance. Another example is, when using a "web-installer" (think WordPress updates). All these changes will not be reflected in Git — as it is not a good practice to store such runtime data in Git and as there is no way, to sync back those changes to the Git repo (so you could pull these changes back in). It's not possible and it's also not what you want.

There are multiple approaches to deal with this situation, the two most common patterns are:

1. Most professional is to follow the 12-factor design pattern: Code and content are strictly separated. User generated content will be stored off-site. With each Git push, the code base will be re-packaged and re-deployed. The storage for the Apps is ephemeral, on each (atomic) deployment the complete code base will be replaced with the new contents. The Professional Stack with fortrabbit is designed like that.

2. More convenient — especially for legacy thinking/design — is a solution like the fortrabbit Universal Stack, where during deployment new files from the Git repo will be "synced" in the webspace, with "overwrite but do not delete". The webspace is persistent and one can login via SSH/SFTP to grab and download all the files, when necessary.

Please ask carefully. This question might not be general enough to be of interest for Stack Overflow.