gravitee-io / issues

Gravitee.io - API Platform - Issues
64 stars 26 forks source link

[AM] - Theme edition page desn't render correctly #8654

Closed NathanFirmo closed 1 year ago

NathanFirmo commented 1 year ago
  1. πŸ’₯

    Describe the bug

    Theme edition page desn't render correctly, because the css file is not loaded.

  2. πŸŒ„

    To Reproduce

    Steps to reproduce the behaviour:

1. Install Gravitee AM on docker as described in [docs](https://docs.gravitee.io/am/current/am_installguide_docker_compose.html). 2. Go to settings > theme . 3. See the error

![image](https://user-images.githubusercontent.com/79997705/202271169-35bf3a7d-c21e-4198-9453-5744345e1500.png)

  1. 🌈

    Expected behaviour

    It should be able to render correctly.

![image](https://user-images.githubusercontent.com/79997705/202276133-ed6ea377-9f19-4f51-b737-2d8e0966317d.png)

  1. Current behaviour

    The css assets were not found.

![image](https://user-images.githubusercontent.com/79997705/202271748-6c7e524f-b643-45cf-8a67-5ce3b54899ce.png)

  1. πŸ’»

    Desktop:

    OS : Pop!_OS 22.04 LTS x8664 Kernel : 6.0.6-76060006-generic CPU : AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8) @ 2.100GHz GPU : AMD ATI Radeon Vega Series / Radeon Vega Mobile Series Memory_ : 17866MiB

What are the impacted versions? 3.19.2

  1. πŸš€

    Workaround

Expose the port of the Web UI container intead of use nginx to access it. First you need to add the "ports" prop at webui service in docker-compose.yml.

webui:
 image: graviteeio/am-management-ui:$

 {GIO_AM_VERSION} 

container_name: gio_am_webui
 restart: always
 ports:

*   8080:8080
     depends_on:
*   management
     environment:
*   MGMT_API_URL=[http://localhost:$](http://localhost:$)([http://localhost:$](http://localhost:$)) {NGINX_PORT}/am
     - MGMT_UI_URL=[http://localhost:$](http://localhost:$)([http://localhost:$](http://localhost:$)){NGINX_PORT}

/am/ui
 volumes:

*   ./logs/am-webui:/var/log/httpd
     ~~~
     Then you need to run ****docker compose up**** again and finally open web ui in **[http://localhost:8080**](http://localhost:8080**)([http://localhost:8080**](http://localhost:8080**)) instead of **[http://localhost:80/am/ui**](http://localhost:80/am/ui**)([http://localhost:80/am/ui**](http://localhost:80/am/ui**)).
leleueri commented 1 year ago

Thanks for highlighting this issue. We reproduced it and we will work to fix it as soon as possible.

remisultan commented 1 year ago

This was fixed apparently On latest 3.19 and above

image