Reviewboard page not rendering properly

48 views
Skip to first unread message

Renuka Pampana

unread,
Oct 3, 2023, 5:26:16 AM10/3/23
to Review Board Community
Hi All

I am trying to install latest reviewboard with docker on linux.
I could able install reviewboard through docker on centos system but the reviewboard page is displayed properly 

I have followed the steps as below

docker-run command :
docker run -P --name review54 -v /var/www/reviewboard1:/site -p 9001:8080 -v /etc/httpd:/etc/httpd -e DOMAIN=xxx -e COMPANY="xxx" -e MEMCACHED_SERVER=testbng1.rma.lan:11211 -e DATABASE_TYPE=mysql -e DATABASE_SERVER=testbng1 -e DATABASE_USERNAME=rb  -e DATABASE_NAME=reviewboard -e DATABASE_PASSWORD=testbng -v /var/lib/mysql:/var/lib/mysql -v /var/run/mysqld:/var/run/mysqld beanbag/reviewboard:latest

container logs shows 
File "/venv/lib/python3.8/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 167, in _get_response
    callback, callback_args, callback_kwargs = self.resolve_request(request)
  File "/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 290, in resolve_request
    resolver_match = resolver.resolve(request.path_info)
  File "/venv/lib/python3.8/site-packages/django/urls/resolvers.py", line 589, in resolve
    raise Resolver404({'tried': tried, 'path': new_path})
django.urls.exceptions.Resolver404: {'tried': [[<URLResolver <module 'reviewboard.urls' from '/venv/lib/python3.8/site-packages/reviewboard/urls.py'> (None:None) ''>, <URLResolver <module 'djblets.extensions.urls' from '/venv/lib/python3.8/site-packages/djblets/extensions/urls.py'> (None:None) 'admin/extensions/'>], [<URLResolver <module 'reviewboard.urls' from '/venv/lib/python3.8/site-packages/reviewboard/urls.py'> (None:None) ''>, <URLResolver <module 'reviewboard.admin.urls' from '/venv/lib


le "/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 43, in get_templatetag_libraries
    libraries = get_installed_libraries()
  File "/venv/lib/python3.8/site-packages/django/template/backends/django.py", line 98, in get_installed_libraries
    for app_config in apps.get_app_configs())
  File "/venv/lib/python3.8/site-packages/django/apps/registry.py", line 145, in get_app_configs
    self.check_apps_ready()
  File "/venv/lib/python3.8/site-packages/django/apps/registry.py", line 136, in check_apps_ready
    raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.


During handling of the above exception, another exception occurred:
Lot of errors djablets

 self.check_apps_ready()
  File "/venv/lib/python3.8/site-packages/django/apps/registry.py", line 136, in check_apps_ready
    raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
[2023-10-03 07:02:24 +0000] [23] [DEBUG] Closing connection.
[2023-10-03 07:02:24 +0000] [20] [ERROR] Error handling request /static/djblets/js/jquery.gravy.min.2ec0ba4d2fa3.js
Traceback (most recent call last):
  File "/venv/lib/python3.8/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 167, in _get_response
    callback, callback_args, callback_kwargs = self.resolve_request(request)
  File "/venv/lib/python3.8/site-packages/django/core/handlers/base.py", line 290, in resolve_request
    resolver_match = resolver.resolve(request.path_info)
  File "/venv/lib/python3.8/site-packages/django/urls/resolvers.py", line 589, in resolve
    raise Resolver404({'tried': tried, 'path': new_path})


How to resolve this issue? Do i have to install any package

Thank you for your help.

Thanks
Renuka
reviewboard.PNG

Christian Hammond

unread,
Oct 3, 2023, 5:46:25 AM10/3/23
to revie...@googlegroups.com
Hi Renuka,

The Review Board container won’t serve up static media (CSS, JavaScript, images, or uploaded files). You’ll need to have a web server container in front of it. We recommend nginx for this.

If you look at the sample docker-compose files, you’ll see how these link up. All requests go to nginx, and then nginx will serve up the static media files or forward on to the Review Board container.

Christian

--
Christian Hammond
President/CEO of Beanbag
Makers of Review Board


--
Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups "Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/7391e4c8-8136-4262-a551-e4351d2ed6b6n%40googlegroups.com.

jeannoel Chiganne

unread,
Oct 26, 2023, 4:32:59 AM10/26/23
to Review Board Community
Hello,

Just in case, I got this problem with the github docker-composer/nginx setup.
There seems to be an error in the "default.conf.template" nginx file.

At the end of the file, the various "location" sections refer to a wrong directory.
It should be like this (the alias must point to "reviewboard" and not what it is in the github official repo):

    location /media/ {
      alias /var/www/reviewboard/htdocs/media/;
      expires max;
      add_header Cache-Control public;
    }

    location /static/ {
      alias /var/www/reviewboard/htdocs/static/;
      expires max;
      add_header Cache-Control public;
    }

    location /errordocs/ {
      alias /var/www/reviewboard/htdocs/errordocs/;
      expires 5d;
    }

    location /robots.txt {
      alias /var/www/reviewboard/htdocs/robots.txt;
      expires 5d;
    }

Christian Hammond

unread,
Oct 26, 2023, 4:54:58 PM10/26/23
to revie...@googlegroups.com
Thanks for pointing this out. We had this correct for Review Board 5, but looks like it was unintentionally changed for Review Board 6 while we were working on documentation updates.

We'll get this fixed ASAP.

Christian

Reply all
Reply to author
Forward
0 new messages