Bug: raptor not found

[fabiangabel]

Description of Bug

After starting the container, the application in the web browser is not accessible but the error message raptor not found. shows up, see the screenshot below

Steps to Reproduce

Use the current repository on Linux Mint 20.2 and carry out the docker installation instructions as provided in README.md.

Further Infos

I used git bisect to find the commit that may have broken the app:

6307b7123cd61bdbdccd43716cff5d65ab9e34e8 is the first bad commit
commit 6307b7123cd61bdbdccd43716cff5d65ab9e34e8
Author: K. Andrew Parker <kparker@citytech.cuny.edu>
Date:   Thu Jul 15 16:03:51 2021 -0400

    minimal access in production mode

 lib/RenderApp.pm                       | 48 ++++++++++++--------
 lib/RenderApp/Controller/Render.pm     | 80 ++++++++++++++++++----------------
 templates/exception.production.html.ep | 27 ++++++++++++
 3 files changed, 100 insertions(+), 55 deletions(-)
 create mode 100644 templates/exception.production.html.ep

Here ist the complete trajectory of my git bisect

container$ git bisect log
git bisect start
# bad: [d2d844efa2f7a2a651b1ba91cfb49e5ff48a84a1] Merge pull request #62 from drdrew42/feature/strict-production-mode
git bisect bad d2d844efa2f7a2a651b1ba91cfb49e5ff48a84a1
# good: [cb433f7607965c4f0a9c6c9b97be0a4e17ddaf9c] add jwt/jwe-generator endpoints
git bisect good cb433f7607965c4f0a9c6c9b97be0a4e17ddaf9c
# good: [084fec0860edc4f83dd6d5c3b58d246fda7c4dc0] Merge pull request #60 from pstaabp/update-install-instructions
git bisect good 084fec0860edc4f83dd6d5c3b58d246fda7c4dc0
# bad: [6307b7123cd61bdbdccd43716cff5d65ab9e34e8] minimal access in production mode
git bisect bad 6307b7123cd61bdbdccd43716cff5d65ab9e34e8
# good: [7fc2e5cf40d5cf8d51df7a8b4796e82968fd915b] Merge pull request #61 from drdrew42/feature/jwt-jwe-api
git bisect good 7fc2e5cf40d5cf8d51df7a8b4796e82968fd915b
# first bad commit: [6307b7123cd61bdbdccd43716cff5d65ab9e34e8] minimal access in production mode

[taniwallach]

PR #62 was intended to make the development features (such as the editor page and far more) only available when MOJO_MODE is set to development, as well as to require using a problemJWT when making requests in production mode.

The Dockerfile currently sets MOJO_MODE=production which us what breaks the access to the local editor on localhost:3000 .

There was a change in the PR which was supposed to use the render_app.conf.dist or render_app.conf file to set the MOJO_MODE, but it apparently does not work as @drdrew42 intended, at least not for Docker setups.

I think that the simplest fix to get back the editor for now is to edit Dockerfile and to replace the line

ENV MOJO_MODE=production

with

ENV MOJO_MODE=development

and then to rebuild the container. That seems to work around the issue for now.

[fabiangabel]

Yes, I confirm that this fixed the issue for me.

[Miniland1333]

Could you please confirm if #72 closes this issue or if you think that additional work needs to be done?

[fabiangabel]

Yes, #72 solves the issue for me.

[Miniland1333]

Closed by #72