-
Notifications
You must be signed in to change notification settings - Fork 146
Documentation compilation is broken #90
Comments
This is a stopgap measure to prevent builds from failing. See #90.
@musale Any chance you can look into this? |
Hi @isms |
The problem is that the docs rely on Django, but it is not present in the prediction/requirements. Also, may I ask why the "restart: always" was added (I'm new to Docker)? With the above error, it caused the build to run in an endless loop for me, because it tried to restart on every failure. |
Hello @ask7 I tried using the When I run:
Everything builds but the container won't finish building because the compile_docs_1 | Postgres is unavailable - sleeping
compile_docs_1 | Postgres is unavailable - sleeping When I run:
Everything builds but I get
current stateI am separating the import os
os.envrion['DJANGO_SETTINGS_MODULE'] = 'interface.config.settings...' But that doesn't seem to recognize the restart: alwaysSince the documentation is done in two separate containers i.e. |
@musale Thanks for explaining I think it's a good idea to separate the two requirements and configs. Did you also set
? I'm not sure you can simply use the settings files of |
As of fc898d4 the requirements have been untangled, but somebody needs to take a look at the actual building part and decide where the logic should live. |
The new Docker services introduced by #55 to compile documentation are not currently working.
Expected Behavior
We expect on
docker-compose -f local.yml up --build compile_docs
for the documentation to build properly.Current Behavior
We currently get numerous stack traces:
Possible Solution
There seem to be two problems:
Packages are not being installed, e.g. Django. See for example:
The presence or absence of
__init__.py
are cause module errors.Steps to Reproduce
compile_docs
container withdocker-compose -f local.yml up --build compile_docs
The text was updated successfully, but these errors were encountered: