Open aaaaalbert opened 10 years ago
@asm582, want to have a shot?
Ok i will work on this...
Found changes in the below files:- local_template/settings.py settings_base.pyc html/templates/base.html html/templates/download_keys.html html/templates/download_installers.html html/templates/builder.html
Since our DJANGO_SETTINGS_MODULE is local.settings so i think DJANGO expects the constants to be placed under custominstallerbuilder/local/settings.py and i have initialized context_processor.py from settings_base.py.
@lukpueh...?
The current custominstallerbuilder HTML has lots of mentions of "Seattle", Seattle-specific terminology, and "Custom Installer Builder". These are hardcoded which makes it hard for people forking the custominstallerbuilder to, e.g., use a different testbed name than we do.
The obvious fix is to replace said instances by constants that will be substituted by Django using the
{{ CONSTANT_NAME }}
syntax in the HTML code, and defining these constants inlocal_template/settings.py
. (Grep the sources forMEDIA_URL
to get an idea how this approach works).(See also SeattleTestbed/clearinghouse#139)