goferfs

Gofer Filesystem

Note: this is beta status and things should work, but changes are still very possible

The goal of this library is to provide a high level common API surface for manipulating files, regardless of where they're actually stored, be it locally, or in the cloud, like Amazon S3.

It should be able to easily swap in different adapters (i.e. s3 and local are (planned) adapters).

Installing

To install, you have to install the Gofer core, and at least one adapter (in this example, the Local Adapter):

npm install goferfs goferfs-adapter-local

API

The API is pretty straight forward:

import Gofer from 'goferfs';
import LocalAdapter from 'goferfs-adapter-local';
import { Visibility } from 'goferfs/types';
 
const gofer = new Gofer(new LocalAdapter({ rootPath: '/path/to/root' }));
 
(async () => {
    // write a file (overrides contents if it already exists)
    await gofer.write('test.txt', 'Contents');
 
    // reading a file is straightforward:
    const { contents } = await gofer.read('test.txt');
    console.log(contents); // "Contents"
 
    // files are wrapped in metadata
    const file = await gofer.read('test.txt');
    console.log(file); // prints something like:
    {
        name: 'test.txt',
        ext: '.txt',
        path: 'test.txt', // these are relative to the rootPath passed in the constructor
        parentDir: '.', // these are relative to the rootPath passed in the constructor
        size: 8,
        isFile: true,
        isDir: false,
        timestamp: Date('2016-12-22T20:17:27.000Z'),
        mimetype: 'text/plain',
        contents: 'Contents',
    }
 
    // if the directory doesn't exist, one is created for you
    const metadata = await gofer.write('this/path/does/not/yet/exist/test.txt', 'Contents');
    // (this returns all of the same metadata above except `contents`)
 
    // you can check to see if a file or directory exists:
    const exists = await gofer.has('does/not/exists'); // exists === false
 
    // you can delete a file
    await gofer.delete('test.txt');
 
    // you can also (recursively) delete a dir
    await gofer.deleteDir('some/dir');
 
    // you can create an empty dir (or do nothing if it existed already)
    await gofer.createDir('some/other/dir');
 
    // you can even copy and move (aka rename) files:
    await gofer.copy('test.txt', 'test2.txt');
    await gofer.move('test.txt', 'test1.txt');
 
    // it, of course, supports streams
    await gofer.writeStream('test.txt', someReadableStream);
    const { stream } = await gofer.readStream('test.txt');
    // returns a StreamFile, which is same as File, but has a `stream` property instead of `contents`
    
    // you can also set the visibility (does different things depending on adapters.
    // the Local Adapter lets you set the permission mask (configurable in constructor))
    await this.setVisibility('test.txt', Visibility.Private);
    (await this.getVisibility('test.txt')) === Visibility.Private;
})();

The API always returns a promise (some adapters may be able to do certain things synchronously, but for consistency, it returns promises as some adapters have to do thing async).

Planned Features

Caching

We want to make it so you can cache files, so if you are using cloud storage, you can cache files in Redis/memory/locally for faster access.

Easy switching between adapters

We want to have it so you can easily use multiple adapters:

const gofer = new GoferManager({
  s3: s3Adapter, // Amazon S3
  gcs: gcsAdapter, // Google Cloud Storage
});
 
gofer.write('s3://test.txt', 'Contents');
gofer.rename('s3://test.txt', 'gcs://test.txt');

Lots of Adapters

Pretty self-explanatory

Easy way to create your own adapter

We're using TypeScript so we can use interfaces that Adapters can implement, so it will be relatively easy to create a new adapter following that pattern (you don't have to use TypeScript, of course, it should help, though).

We also are working on a test suite so you can basically call testSuite(myAdapter) and it will run a bunch of tests to use as a good benchmark to get adapters working.

Contributing

In these early stages, we would love some feedback on the interfaces, especially. I would definitely not be writing any adapters based on this yet, but once the API is stabilized, it would gladly welcome contributed adapters for various services. (The idea is that each adapter (except maybe local and memory?) will be in its own repo.)

Similarities to the PHP League's Flysystem

This was heavily inspired by the awesome PHP package by the PHP League: Flysytem. They definitely deserve some credit here.