django version in requirements

[eipVCCRI]

Hi Daniel,

How are you doing?

I have been asked to setup this year's ABACBS abstract submission webpage.

I have question about the django version in the requirement setup. I noticed that there is an activity log regarding a change in version, but it is not in the master. I do have an issue running the "python manage.py migrate" after doing the "pip install -r requirements/local.txt".

We did use your code back in 2019, and Michael Troup (who set it up) had downgrade the Djanjo version to 2.0.13, for query table issue, based on your recommendation. I also tried this, but did not help. Unfortunately Michael is not around at the moment for me to ask.

Hope you can help.
Eddie (VCCRI)

[eipVCCRI]

I see the activity is from a Dependabot change.

[daniaki]

Hey Eddie, apologies for the delayed response. What issues are you running into when you run those commands? This project is no longer being maintained and is running on an old version of Django that is also no longer maintained, which probably has unpatched security vulnerabilities. You can try upgrading to Django 3+ LTS or Django 5, however there may be some things that break because of deprecated functions.

[eipVCCRI]

Hi Daniel.

No problem and thanks for answering.

You are right in guessing that it has to do with depreciated functions. I will take on your suggestion and move forward in Django versions, instead of back.

I have another question. The Secret json file has a field for "secret_key". I don't know what this is or where to find it. I had guessed it was the secret key that is in the created ABACBSAbsSS/settings.py file. Is this correct, or is it something else?

Thanks
Eddie

[daniaki]

I suggest reading the upgrade guide on the official Django website, and to make sure all tests are passing after the upgrade.

Django uses a secret key for security purposes and you will need one to run the application. You can generate one from the command line (assuming you have django installed):

python -c 'from django.core.management.utils import get_random_secret_key; print(get_random_secret_key())'

Do not check this into Github if you're running from your own fork.

[eipVCCRI]

Thanks. Will do.

So the secret key I found in the settings.py is correct.

Thanks