You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Albert Martin ba1543e3e8 Persist current team when using token auth (#616) 8 years ago
bin Option `--session-affinity` was added for setting session affinity (#600) 8 years ago
download Download from GitHub directly (#625) 8 years ago
lib Persist current team when using token auth (#616) 8 years ago
link Throw an error if current path doesn't exist 8 years ago
scripts Fix Slack script 8 years ago
test Removed build step 8 years ago
.gitignore Build inside a single directory 8 years ago
.npmrc Save exact version of dependencies 8 years ago
.travis.yml Show the diff 8 years ago
license.md Lowercased text files 8 years ago
package.json chore(package): update node-fetch to version 1.7.1 (#627) 8 years ago
readme.md Slight improvements to reasons for shipping a `pkg`-ed binary 8 years ago

readme.md

now CLI

Build Status XO code style Slack Channel

This is the command line interface for now: Realtime global deployments served over HTTP/2.

It's also a special kind of package. When you install it using npm install -g now, it will automatically select the latest version of the pkg-ed now binary from here and place it on your device.

Usage

Simply follow this guide! Then run this command to see a list of all commands:

now help

Why Ship a pkg-ed Binary?

  • Simpler installation for non-Node users like those deploying static files or Dockerfiles.
  • Consistency across platforms and installation mechanisms (npm, brew and manual scripts)
  • Parsing and evaluation optimizations lead to a faster bootup time
  • Easier installation in automation environments (like CI systems)
  • Increased safety by providing a unified signature mechanism for releases
  • We're able to select our own Node version of choice and can take advantage of the latest features

Caught a Bug?

  1. Fork this repository to your own GitHub account and then clone it to your local device
  2. Link the package to the global module directory: npm run link (not npm link)
  3. You can now start using now from the command line!

As always, you can use npm test to run the tests and see if your changes have broken anything.

Authors