Skip to content

Setup deployed backend structure in web container.

After a discussion today, we agreed that it would be better to simply mount whole deployed backend environment into the freva_web container. This has the following advantage(s):

  • evaluation_system.conf would always be the same. Admin changes of the config file in the backend would immediately be applied in the web.
  • The changes in the backend code would also be in effect.

Hence this rather small MR. Here we do the following:

  • Check if the backend has already been deployed resp if the backend is available on the deploy machine. If not raise an Error.
  • Deploy the freva web using the the path to the backend as a volume. Here we set the PYTHONPATH variable to make it visible for python.

@k204225 can you check which folders (in addition to preview) should be added as a volume. @k204231 fyi

Merge request reports