uploadfs | Store files in a web-accessible location

uploadfs is a JavaScript library typically used in Telecommunications, Media, Media, Entertainment applications. uploadfs has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i uploadfs' or download it from GitHub, npm.

The init method passes options to the backend and invokes a callback when the backend is ready. The optional destroy(callback) method releases any resources such as file descriptors and timeouts held by uploadfs. The copyIn method takes a local filename and copies it to a path in uploadfs. (Note that Express conveniently sets us up for this by dropping file uploads in a temporary local file for the duration of the request.). The copyImageIn method works like copyIn. In addition, it also copies in scaled versions of the image, corresponding to the sizes you specify when calling init(). Information about the image is returned in the second argument to the callback. If you wish to crop the image, pass an options object as the third parameter to copyImageIn. Set the crop property to an object with top, left, width and height properties, all specified in pixels. These coordinates are relative to the original image. When you specify the crop property, both the "full size" image copied into uploadfs and any scaled images are cropped. The uncropped original is NOT copied into uploadfs. If you want the uncropped original, be sure to copy it in separately. The width and height properties of the info object passed to your callback will be the cropped dimensions. The default JPEG quality setting for scaled-down versions of your image is 80. This avoids unacceptably large file sizes for web deployment. You can adjust this via the scaledJpegQuality option, either when initializing uploadfs or when calling copyImageIn. If you do not wish to always use the same set of image sizes, you may pass a sizes property as part of the options object when calling copyImageIn. The copyOut method takes a path in uploadfs and a local filename and copies the file back from uploadfs to the local filesystem. This should be used only rarely. Heavy reliance on this method sets you up for poor performance in S3 and Azure. However it may be necessary at times, for instance when you want to crop an image differently later. Heavy reliance on copyOut is a recipe for bad S3 and/or Azure performance. Use it only for occasional operations like cropping. The remove method removes a file from uploadfs. The getUrl method returns the URL to which you should append uploadfs paths to fetch them with a web browser. The disable method shuts off web access to a file. Depending on the storage backend it may also block the copyOut method, so you should be sure to call enable before attempting any further access to the file. The enable method restores web access to a file. The getImageSize method returns the currently configured image sizes. The identifyLocalImage method provides direct access to the uploadfs functionality for determining the extension, width, height and orientation of images. Normally copyIn does everything you need in one step, but this method is occasionally useful for migration purposes. The destroy method releases any resources such as file descriptors or timeouts that may be held by the backends, and then invokes its callback. Its use is optional, but command line Node apps might never exit without it.