Multiple static paths / serve `MEDIA_URL` from `MEDIA_ROOT` (Django)

[muety]

For my Django application, I'm currently using GRANIAN_STATIC_PATH_ROUTE and GRANIAN_STATIC_PATH_MOUNT to serve static assets from STATIC_ROOT as STATIC_URL. However, there is MEDIA_ROOT and MEDIA_URL to be served as well, so I'd need Granian to accept a list of static folders and according paths.

[gi0baro]

Tbh, I don't think completely offloading user uploads to the server is a good idea. That kind of "media" usually requires additional application checks/code compared to static assets.

While I don't know if and when Granian will ever support multiple static paths (I don't necessarily see advanced routing to be a fit for a server), I'd say frameworks like Django might benefit from implementing support for protocol-related file facilities, like ASGI pathsend.

[muety]

Tbh, I don't think completely offloading user uploads to the server is a good idea. That kind of "media" usually requires additional application checks/code compared to static assets.

Django itself takes care of the whole upload procedure, there's nothing the web server would have to be concerned with. The only thing that Granian needs to do is serve static files from the respective directory, just like what it's already doing for anything configured via GRANIAN_STATIC_PATH_* – nothing more, nothing less. It's completely framework-agnostic.

Would really appreciate if Granian would implement this.

Edit: What I'm looking for is pretty much exactly what uWSGI implements as static-map.

[gi0baro]

Would really appreciate if Granian would implement this.
What I'm looking for is pretty much exactly what uWSGI implements as static-map.

I understand, my point being such change would make Granian code more complicated.

Given Django allows you to configure all of the involved variables, what prevents you to use the same parent folder and prefix for both of them? eg:

STATIC_ROOT={COMMON_PATH}/static
STATIC_URL=/assets/static
MEDIA_ROOT={COMMON_PATH}/media
MEDIA_URL=/assets/media
GRANIAN_STATIC_PATH_MOUNT={COMMON_PATH}
GRANIAN_STATIC_PATH_URL=/assets

[muety]

Would be possible, but would also require to update URLs throughout my entire application, including files paths / URLs referenced in the database, etc. I'd prefer if Granian would implement sth. like static-map, esp., because it's not only a Django-related issue but could be handy in general, regardless of the underlying web framework.

[parasiteoflife]

I don't know if this is intended but when I run granian under Windows it serves the media folder without specifying any option. When I run the same app in alpine I have to set both GRANIAN_STATIC_PATH_MOUNT and GRANIAN_STATIC_PATH_URL for it to serve the media directory.

[sirikon]

Just to add more use cases: I'm developing a Django-based app that is distributed as a Docker container. It has both Django's STATIC files and MEDIA files.

STATIC files are bundled with the app, while MEDIA files are intended to be backed up by the Docker container's operator. To ease this up for the operator, there's a directory called /w with all the stuff that needs to be backed up.

In this scenario, I need Granian to serve dir /app/static under url /static, dir /w/media under url /media, and maintain both directories separated so static files are not backed up.

If Granian supported symlinks (mentioned in #680), and being a completely new app unlike @muety 's situation, I could live with serving dir /static under url /static and creating symlinks to /w/media and /app/static inside /static. That said, I would strongly prefer being able to define multiple mounting points for static files.

My current scrappy solution is to bundle Caddy in the Docker container and use it to serve static files and proxy non-static requests to Gunicorn, which runs in tandem in the same container.