Create native GridFS integration (or document recipes)

How can we specify the GridFS collection name (not the FilesCollection collectionName)? It defaults to fs. and I cant get it to accept new name.

[macrozone]

a small improvement over @hluz ’ suggestion above:

// interceptDownload
 .on('error', err => { throw err; })

this is bad, because if it can’t read the file, this will crash the server. Better handle it:

interceptDownload(http, file, versionName) {
      const { gridFsFileId } = file.versions[versionName].meta || {};
      if (gridFsFileId) {
        const readStream = gridFSBucket.openDownloadStream(new ObjID(gridFsFileId));
        readStream.on('data', (data) => {
          http.response.write(data);
        });

        readStream.on('end', () => {
          http.response.end('end');

        });
        readStream.on('error', () => {
          // not found probably
          // eslint-disable-next-line no-param-reassign
          http.response.statusCode = 404;
          http.response.end('not found');
        });
        http.response.setHeader('Cache-Control', this.cacheControl);
        http.response.setHeader('Content-Disposition', `inline; filename="${file.name}"`);
      }
      return Boolean(gridFsFileId); // Serve file from either GridFS or FS if it wasn't uploaded yet
    },

EDIT: i forget to set the cache control!

[dr-dimitru]

@hluz no worries.

Actually we wish to fork gridfs-stream and keep it in up-to-date shape 😃 . We all were sad to discover it in a such badly maintained state. Or maybe @aheckmann could give us a push rights to repository, or better transfer it to us (including NPM)? @aheckmann if you’re reading this, take a look at our experience, for years we keep many packages in up-to-date state, taking care of every ticket and PR. Consider giving your child into good hands 😃