Closed lukpueh closed 8 years ago
You don't seem to be missing anything (apart from the correct information at the correct place, of course!)
/var/www/dist
is indeed the "magic" / historic / agreed upon home directory for base installers. They'll actually end up below that in installers/base_installers
IIRC, and the generated installers are cached in installers/RANDOM_HASH_ID
.
In general you are free to choose whatever base installer dir. You are right that the CIB docs page should mention this, and so should the infrastructure architecture page.
Speaking with @lukpueh we arrived at the conclusion that the underlying problem is a synchronization issue between documentation and implementation currently. The docs assume "the old way" of building installers that used a specific build shellscript. Current and future CIBs however use @XuefengHuang's Python port of this script which internally assumes a certain dir layout pre-generated by the new Seattle buildscripts in order to work.
In other words, the CIB docs must be adapted to a significant degree. See SeattleTestbed/docs#15.
I wonder if the CIB installation docs are misleading. When I setup the CIB django app as suggested I get the following error when I try to download the installer:
As far as I understand the custom installer bundle is created by
common/packager.py
which builds/packages it from the base installer atBASE_INSTALLER_ROOT
-- a default setting found insettings_base.py
that points to the directory seen in the error message above.The docs don't mention to change this setting. But they do suggest to install the base installers at
/var/www/dist
this section.Am I missing something?