This method is not recommended, but there are solutions: 1. Develop an interface, and the interface parameters can uniquely identify 'the path stored in the database' 2. Use the IO stream in the interface, get the path according to the database, and read the IO Return to the client I think the normal solution is: 1. Create a new directory locally to store your files and save the relative path. For example, if you create this level directory src, it will be doc/abc.doc. Then what you save in the database is doc/abc.doc 2. Use nginx and other configurations to configure the external network to access the directory. Configure the root directory to src, and that’s it
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
IO streams. . . .
This method is not recommended, but there are solutions:
1. Develop an interface, and the interface parameters can uniquely identify 'the path stored in the database'
2. Use the IO stream in the interface, get the path according to the database, and read the IO Return to the client
I think the normal solution is:
1. Create a new directory locally to store your files and save the relative path. For example, if you create this level directory src, it will be doc/abc.doc. Then what you save in the database is doc/abc.doc
2. Use nginx and other configurations to configure the external network to access the directory. Configure the root directory to src, and that’s it