A cloud-based Dropbox® equivalent for browser filesystems. Designed for use with Mozilla Webmaker tools and services.
See the Mozilla MakeDrive Wiki page for background info.
- Node.js: v0.10+
- Clone the MakeDrive repository.
$ git clone https://github.com/mozilla/makedrive.git
- In your MakeDrive directory, install all of the necessary MakeDrive dependencies:
If you don't already have grunt-cli installed globally, here is the console command using npm -
$ sudo npm install grunt-cli -g
Afterwards, install the npm modules -
$ npm install
Next, install submodules' dependencies -
$ grunt init
- Copy the distributed environment file via command line, or manually using a code editor:
$ cp env.dist .env
- Run the MakeDrive server:
$ npm start
You will now have MakeDrive running on localhost via port 9090 - http://localhost:9090
An independent and lightweight front-end instance has been added to test MakeDrive's functionality on its own.
The NODE_ENV variable must be set to development in your .env file for this page to be enabled.
It currently resides on and can be visited at localhost:9090/demo/?makedrive=ws://localhost:9090.
NOTE: For connecting the demo with another MakeDrive server, the localhost address and port of the above demo page must be added to the ALLOWED_CORS_DOMAINS variable in the .env file of
the instance you are trying to connect to in order to avoid cross-origin resource errors.
Built on top of the Filer filesystem interface, MakeDrive adds cloud-like syncing functionality that allows for multiple clients to share and interact with an active project directory from different browsers or platforms. There are features and options for both manual and auto syncing.
Below is a simple way to create and initiate a MakeDrive instance on client-side code:
var fs = MakeDrive.fs();
Multiple calls to MakeDrive.fs() will return the same instance.
MakeDrive has three HTTP REST endpoints for retrieving user filesystem data in various formats. All of these routes require authentication and are not meant for public use, but for users and apps to allow easy access to data when logged in.
Each one is accessed by simply being appended to the URL that presently hosts MakeDrive
(eg. https://makedrive.mofostaging.net/p/):
/p/ - Serves as a path for a user's Filer filesystem. You can currently view anything that has been synced inside of the user's project directory tree.
/j/ - Similar to the /p/ route, but serves the path information in JSON format for APIs.
/z/ - Used to export the current user's project data in compressed ZIP format.
###Constructor
var fs = MakeDrive.fs({
manual: true,
memory: true,
forceCreate: true
// etc.
});A number of configuration options can be passed to the fs() function.
These include:
| Option | Value | Definition |
|---|---|---|
manual |
true |
by default the filesystem syncs automatically in the background. This disables it. |
memory |
<Boolean> |
by default we use a persistent store (indexeddb or websql). Using memory=true overrides and uses a temporary ram disk. |
provider |
<Object> |
a Filer data provider to use instead of the default provider normally used. The provider given should already be instantiated (i.e., don't pass a constructor function). |
forceCreate |
<Boolean> |
by default we return the same fs instance with every call to MakeDrive.fs(). In some cases it is necessary to have multiple instances. Using forceCreate=true does this. |
interval |
<Number> |
by default, the filesystem syncs every minute if auto syncing is turned on, otherwise the interval between syncs can be specified in ms. |
windowCloseWarning |
<Boolean> |
false by default. When toggled to true, prompts the user to confirm exiting the webpage when trying to close in the middle of a sync. |
Various bits of Filer are available on MakeDrive, including:
MakeDrive.Buffer
MakeDrive.Path
MakeDrive.Errors
See Filer's docs for more information.
The filesystem instance returned by MakeDrive.fs() includes
the property sync. The fs.sync property is an EventEmitter
which emits the following events:
| Event | Description |
|---|---|
'error' |
an error occurred while connecting/syncing. The error object is passed as the first arg to the event. |
'connected' |
a connection was established with the sync server |
'disconnected' |
the connection to the sync server was lost, either due to the client or server. |
'syncing' |
a sync with the server has begun. A subsequent 'completed' or 'error' event should follow at some point, indicating whether or not the sync was successful. |
'completed' |
a sync has completed and was successful. |
The sync property also exposes a number of methods, including:
| Method | Purpose |
|---|---|
connect(url, [token]) |
Try to connect to the specified sync server URL. An 'error' or 'connected' event will follow, depending on success. If the token parameter is provided, that authentication token will be used. Otherwise the client will try to obtain one from the server's /api/sync route. This requires the user to be authenticated previously with Webmaker. |
disconnect() |
Disconnect from the sync server. |
request() |
Request a sync with the server. The path is automatically tracked by any changes that occur within the filesystem. Such requests may or may not be processed. |
Finally, the sync property also exposes a "state", which is the
current sync state and can be one of:
sync.SYNC_DISCONNECTED = "SYNC DISCONNECTED" /* also the initial state */
sync.SYNC_CONNECTING = "SYNC CONNECTING"
sync.SYNC_CONNECTED = "SYNC CONNECTED"
sync.SYNC_SYNCING = "SYNC SYNCING"
sync.SYNC_ERROR = "SYNC ERROR"Any assistance in adding new features or enhancing current ones, as well as resolving issues is greatly appreciated. Please refer to our CONTRIBUTING.md document for more information about internal MakeDrive implementations, git conventions and testing methodologies for aspiring developers.