I am not sure how to deal with the local_settings.py. I understand what most of the variables do, but that is not my concern here. Is it necessary? Why is it in a separate file, and not just listed with the other changes that I should do to settings.py in the Installation section of the documentation? Or why is the list of changes in that section not all just in the local_settings.py? Where is the logical division between those two groups of settings? Does local_settings.py override values in settings.py, or the other way around?
Let's say I want to use a different database than the default simple.db. That is specified in the local_settings.py, which is (in most situations) placed somewhere in the site-packages library.
1) Am I supposed to edit that file then, which requires root priveleges, and which will affect all other Satchmo instances created with clonesatchmo? 2) Copy local_settings.py somewhere to my 'store' folder, and change it there? 3) Skip the import, and copy the relevant content to settings.py?
If the answer is 2 or 3, then, why does clonesatchmo.py not do that by itself to begin with?
It is called local_settings.py. So that suggests, that it is more local than the settings.py, right? But it resides somewhere write-protected, which suggests the opposite.
In general, local_settings suggests that settings.py is not local. Which it absolutely is. Whereas local_settings is actually global, if one creates several shops with clonesatchmo and does not remove the import of local_settings.py.
What do the proffessinals do, do they maintain the division into settings.py and local_settings.py? Or how?