No, store the files directly on a filesystem and save relative paths to them. This has several benefits:
- faster database migration as it does not contain TBs of data,
- not being directly limited by the location of the storage space - you simply prepend the root to the relative path and work with that one (serve that one to the application clients),
- for certain resources, native HTTP caching thanks to
If-Modified-Since/If-None-Match headers, thus saving client resources1,
- in your case easier implementation of content streaming - by allowing clients of the application to retrieve sections of the video files, by cutting the video file and returning only specific byte range of it by the server.
With files being stored on the filesystem you need to make sure they are in a directory which is publicly available (should it be, of course). You then serve these files directly from the filesystem from their path.
Let's say your application is located at
www is a publicly available directory from the browser. Within the
www directory you would create a new one, eg.
uploads, which would also be publicly available and used to store the files. Should you then serve some file to a client of the application it would be as easy as providing them a URI:
https://domain.com/uploads/videos/my-video.mp4, which would translate to the actual
/home/dyslexit/www/uploads/videos/my-video.mp4 file on the server.
It is however not required to directly copy the structure. Should you need it instead of directly serving the files from a HDD when a file is requested you could instead forward the request to a script checking permissions of the requesting user, denying them access should they not be authorized to access a resource or forwarding them to the file being located anywhere respectively.
1 Obviously this can also be implemented if you store files in a database but requires additional setup and custom header manipulation. When serving files directly from the file system this is mostly native.
Either way, if your business goal is not actually storing files - such as your are creating a data-storage system - but it is merely a side-effect of the business (let's say you want videos in a Facebook-like application), the better choice would probably be to completely outsource file storage to a 3rd party system dedicated to this feature - such as Amazon S3.