A command line interface for editing files from your box, on your local machine.
The perfect partner if you're developing ScraperWiki tools, and want to use your normal text editor like TextMate or Sublime Text.
Supports two alternative workflows:
swbox clone fegy5tq – Makes a local copy of firstname.lastname@example.org
swbox clone g6ut126@free - Makes a local copy of email@example.com
swbox mount fegy5tq - Mounts firstname.lastname@example.org as a local filesystem
npm install -g swbox
(If you'd prefer not to use npm, you can always
git clone this repo and run
./prepublish yourself to get an executable cli.js script which you can add to your
Read the documentation by running
Mounting boxes as local drives requires Fuse and SSHFS. Both are available on the Fuse for OS X homepage.
swbox command line client requires Node.js.
If you are developing
swbox we recommend that you run the following from the directory
containing your git clone:
This will put the command
swbox in the usual location where npm installs binaries (which
should already be on your PATH), and symlink it so that whenever you change this directory,
those changes are live.
If you want to use this local in-development version of swbox with a box, then go to the box's directory and use:
npm link swbox
swbox = require 'swbox' will automatically get your local in-development version of swbox.
swbox updateis no longer required and has been removed.
swbox testruns .coffee or .js tests in /tool/test directory, using Mocha.
swbox push --previewwill show a preview of what would be created/updated/deleted, without changing anything on the remote box.
<boxName>can now include an optional
@boxServersuffix, allowing you to clone and mount boxes on free.scraperwiki.com and ds.scraperwiki.com (eg: via
swbox clone abcd123@freeor
swbox mount wxyz789@ds)
swbox syncrenamed to
swbox pushsince it doesn't actually sync, it removes any files on the destination that aren't present on the local copy.
swbox sync/pushto loop forever when invoked outside of a local box clone
swbox cloneno longer takes an optional destination directory – it will always create a clone, in new directory named after the box, in the current working directory
/swboxsymbolic link in root directory – it's no longer needed
swbox synccommand to synchronise local changes inside a clone, back up to the original box
swbox clonecommand to clone an entire box's contents to your local filesystem
-oworkaround=renameto sshfs options, to allow
gitto rename/update files
swbox updatecommand to download the latest version of swbox