innogames / ltc

Online web application-dashboard for report analyzing,running and online monitoring of load tests started with JMeter
MIT License
197 stars 96 forks source link

Django SECRET_KEY error #45

Open AlanCodega opened 1 year ago

AlanCodega commented 1 year ago

Docker composer image not working anymore leading to this error about SECRET_KEY:

JMeterControlCenter | File "/usr/local/lib/python3.6/site-packages/django/conf/init.py", line 79, in getattr JMeterControlCenter | self._setup(name) JMeterControlCenter | File "/usr/local/lib/python3.6/site-packages/django/conf/init.py", line 66, in _setup JMeterControlCenter | self._wrapped = Settings(settings_module) JMeterControlCenter | File "/usr/local/lib/python3.6/site-packages/django/conf/init.py", line 176, in init JMeterControlCenter | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.") JMeterControlCenter | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty. JMeterControlCenter exited with code 1

After spending few hours in copying paste SECRET_KEY from django to env - yml file and try everythings, i found a temporary solution:

workaround Quick & Dirty:

as suggested in: https://github.com/arcmedia/JmeterControlCenter/issues/3

modify this line inside DockerFile:


RUN apt-get update && \
    git clone https://github.com/innogames/JMeter-Control-Center.git
to this:
RUN apt-get update && \
    git clone https://github.com/innogames/JMeter-Control-Center.git && \
    cd JMeter-Control-Center && \
    git reset --hard 683ec5893b380e109c8971765374076406cef3f9 && \
    cd ..

Long-term fix the maintainer of https://github.com/arcmedia/JmeterControlCenter it's not working anymore for innogames:

Should be nice if someone from Innogames can gently take a look at that.

Many thanks in advance!

chinmayroy commented 1 year ago

To find a proper long-term fix, you should try to identify the root cause of the problem. Check the configuration files of your Django application and see if the SECRET_KEY setting is properly set. You can also check if any recent changes in the application code or dependencies might have caused this issue.

Let me know what's going on........