CODEWITHSUNDEEP
djangosettings
Antonio José
Antonio José

Reputation: 495

Django settings.py

At my project login, some settings.py environment variables are loaded to enable some behaviors:

unit_id = settings.COMPANY

When another user logged in the system changes the value of this variable, through a function, it reflects in all other users who are already active:

settings.COMPANY = "coke"

in this case, all users will see "coke" in settings.COMPANY. I believed this would be in memory and would only apply to the user section in question, because I did not write in the physical file.

I wonder if this is how Django handles the settings.py environment variables: Does it propagate dynamically to all instances opened by all users?

This variable is accessed by context_processors.py, below:


def units(request):
    unit_id = settings.COMPANY

Upvotes: 0

Views: 84

Answers (1)

Nico Griffioen
Nico Griffioen

Reputation: 5405

You should not change settings at runtime.

This is (mainly) because Django doesn't know anything about it's runtime, so it's definitely possible to run multiple instances of the same Django installation. Changing a setting like this will not propagate it to any other processes.

I wonder if this is how Django handles the settings.py environment variables: Does it propagate dynamically to all instances opened by all users?

Django doesn't run an instance for every user. There is one or more (if you for example use something like gunicorn or if you use multiple servers with a load balancer.) processes that listen on a certain port.

To have some changeable setting, you could specify a default value, but you should store something like the active company in the database.

Upvotes: 1

Related Questions