go-recaptcha | handling reCaptcha | Form library

I'm pretty new to docker and, although I've read lots of articles, tutorials and watched YouTube videos, I'm still finding that my image size is in excess of 1 GB when the alpine image for Python is only about 25 MB (if I'm reading this correctly!).

I'm trying to work out how to make it smaller (if in fact it needs to be).

[Note: I've been following tutorials to create what I have below. Most of it makes sense .. but some of it feels like voodoo]

Here is my Dockerfile:

Beginner with Django 3.2. I'm trying to add a Recaptcha V3 from Google on my login screen.

• I'am using django-recaptcha3 well configured
• The logo is showing on my login page
• When debugging the json response when calling ReCaptchaField.clean is OK !

The problem is that the form is not validated "'CustomAuthenticationForm' object has no attribute 'cleaned_data'"

Error occured when I do

I am trying to use Recaptcha v3 in one of my projects. Unfortunately the form.valid_date() method fails all the time with "This field is required.".

Running django-recaptcha.

forms.py looks like this:

I have a problem and I will do the best to explain it, to see if you can help me out.

CONTEXT

I have a system running in a test server, which is set up like a production environment in order to test my code before merging to master and give the go to the production server provider of my client to update the code. This means it runs in DEBUG = False. All good, all perfect for months.

I decided to activate the ManifestStaticFilesStorage setting in order to have a hash number added in my static files, I've used it before and it's a good way to break cache rules when updating files (like CSS rules that refuse to load). There is an issue with cache that may be solvable messing around with the server but that's not an option in this case.

Everything went smoothly:

1. No issues in collectstatic other than a few missing static files (already solved)
2. Static files loaded perfectly

BUT...

THE PROBLEM

This system manages content (images, audio files and custom fonts). When I activated the ManifestStaticFilesStorage setting, all uploaded files started to throw 404 errors (and some occasional 500 error) in the server access log. Meaning, they look like this:

You can see the broken image icon but you can also see the background colores of each square (color which is injected by JS because it can be customized in the custom CMS). These images are uploaded in the CMS and they live in the media folder configured in the settings file.

Of course, if I go to DEBUG = True, everything gets fixed (come on! -.-). I went and recreated production enviroment in local, same issue: DEBUG = False bad, DEBUG = True works

THOUGHTS

• 404 means the file is not there. Guess what? it's there, they all are
• The occasional 500 means permissions. Well, I haven't changed the permissions. Also, permissiones where the same. Also, I'm using WebFaction, it handles all that for me
• Console in browser says network error. In the Network tab it doesn't even show the 404 errors or the few 500 that may appear
• Broken DB? Nope. Besides, if it were broken, DEBUG = True would fail
• Apache error log? Nothing to show for. The access log shows the access errors, meaning errors on file that are correctly placed

So, I ran out of ideas. Maybe someone out there has the answer, I hope so. I will still be trying to solve it but I can use the help, please.

RELEVANT CODE

storage.py

I am using Docker to deploy Python2.7 application with Django1.8. I am facing some issue from last two days and I found error as below.

Docker Image: python:2.7-slim-buster

Error: