@benborges said in Deeplinking media files from external volumes:
right now the URL field in my sqlite table does not point to anything because in the original context of this database, the path to the domain is defined in the config.yaml file but exactly like for the LAMP container, I'm wondering how I can just say to nocodb the media files are at /media/
I think I understand what you are saying. You want https://nocodb.osintukraine.com/media/date/3.MP4 to somehow work. So, this won't work currently because it's not possible to override paths of nocodb like we do in the LAMP app. In the LAMP app, since the app is something we control, it's fine to configure paths the way we want. Doing the same for nocodb is going to cause problems at some point. For example, what it nocodb starts serving things in /media from next release. Or maybe it uses that path already for some internal use, who knows.
So, instead, what do you think of either a) linking these to the LAMP app itself or b) setup a separate LAMP app instance under static.osintukraine.com and make it serve images from there. Nocodb can simple reference this for "static" contents. Would some idea like that work?