#4885 Use WhiteNoise to serve static assets for the Pagure web interface
Merged by pingou. Opened by ngompa.
ngompa/pagure add-whitenoise-static-serving  into  master

Download 4885.patch

In order to make it easier to run Pagure in a containerized environment,
the web frontend needs to be capable of serving all of the frontend static
files. This change introduces WhiteNoise as a dependency that would enable
the Flask application itself to serve the static assets correctly.

This makes it possible to run a Pagure server without Apache or Nginx at all
in a containerized environment for all of the main functions.

Note that the releases folder is still not served through WhiteNoise, and
deployments that have uploading releases enabled will need something to
serve them.

Signed-off-by: Neal Gompa ngompa13@gmail.com

There is normally a performance interest in having apache/nginx server the static files

I don't think it'd be any worse than it what it is right now for proxying the Git HTTP push/pull through Pagure. But if you have an idea of how to measure this, we could do that.

rebased onto d22bf0e295f00d863212b6ad94e5cfcdad7e6803

rebased onto 37fea353cdfcc3011d3fed7d4bc1ed130a87211a

rebased onto 6d9ab3337f7fd913a00d1641af729d648eb5a26a

rebased onto 89f18ee38de1e6cb3ac482f865e6352ed340d763

rebased onto ae308ffe623de8c1396c33db7b24f18c9d58bf53

rebased onto ceedaa1bffaec1dd970c5526ea7df21f4bdb7b23

rebased onto 6a01d5897005391a15eb357d26448948569df5fa

rebased onto 7fd79b52d54d029ab8277ccf3d596e21e1dfe407

rebased onto 4be6bdc507422de75e45d4abd4dd84aa9aa67414

rebased onto 4be6bdc507422de75e45d4abd4dd84aa9aa67414

rebased onto ac1781743d35516f8c91f3516a6e3ce977c995fd

rebased onto 83e1979ca988556b2e44ddbe9d9e4661a4ddb988

Thanks :)

Pull-Request has been merged by pingou

Metadata