The configuration PEM file is being saved somewhere next to the python code [1], which may work just in development. In production the code directories are usually write-protected.
Also Django file uploads are handled [2] in quite specific way - can be configured via backends, stored in a different locations, etc. And this must be followed.
kvbik
commented
3 years ago
The configuration PEM file is being saved somewhere next to the python code [1], which may work just in development. In production the code directories are usually write-protected.
[1] https://github.com/efdevcon/pretix-attestation-placeholder-plugin/blob/main/pretix_attestation_plugin/views.py#L10
Also Django file uploads are handled [2] in quite specific way - can be configured via backends, stored in a different locations, etc. And this must be followed.
[2] https://docs.djangoproject.com/en/3.2/topics/http/file-uploads/
Another way of doing this would be saving the content directly to database as a
TextField.