Hello Kumar,

two comments about this:

1/ you need a reverse proxy only for production system. For a developper instance, using gunicorn directly works perfectly fine. You only need to have a reverse proxy for security reasons (prevent DOS and SSL termination).

2/ In the docker-compose that we provide, the reverse proxy (apache2) will still be provided by default.

Rgds

Le mer. 12 févr. 2020 à 15:09, Kumar Gala <kumar.gala@linaro.org> a écrit :

> On Feb 12, 2020, at 7:21 AM, Remi Duraffort <remi.duraffort@linaro.org> wrote:
>
> Hello everyone,
>
> if you follow the latest developments, you might have seen that LAVA is now using whitenoise to allow gunicorn to serve static files.
> In the current releases (2020.01 and before), apache2 is forwarding dynamic requests to gunicorn and serving static files himself.
> In the next release, apache2 will forward all the requests to gunicorn that will serve both dynamic and static content.
>
> If you use the debian packages, apache2 will still be installed and configured automatically.
>
> We are proposing to drop the apache2 packages from the lava-server docker container. In fact, if you use the docker container, you have anyway to setup a reverse proxy to make the container visible to the outside world and to do the SSL termination.
>
> What do you think about this?

It seems like a step backwards if you know have to do some additional work outside of the container or modifying the container to have a working setup out of the box.

- k