unleash.unleash/docs/getting-started.md

id	title
getting_started	Getting Started

Requirements

You will need Node.js >= 8.0.0 and a PostgreSQL 9.5+ database instance to be able to run Unleash.

When starting Unleash you must specify a database URI (can be set as environment variable DATABASE_URL) which includes a username and password, that have rights to migrate the database.

On startup Unleash will perform necessary migrations if needed.

Start Unleash

1. The simplest way to get started:

$ npm install unleash-server -g
$ unleash -d postgres://unleash_user:passord@localhost:5432/unleash -p 4242

Unleash started on http://localhost:4242

2. Or programmatically:

You can also depend on unleash

const unleash = require('unleash-server');

unleash
  .start({
    databaseUrl: 'postgres://unleash_user:passord@localhost:5432/unleash',
    port: 4242,
  })
  .then(unleash => {
    console.log(
      `Unleash started on http://localhost:${unleash.app.get('port')}`,
    );
  });

Available unleash options include:

• databaseUrl - the postgres database url to connect to. Should include username/password.
• databaseSchema - the postgres database schema to use. Defaults to 'public'.
• port - which port the unleash-server should bind to.
• enableLegacyRoutes (boolean) - allows you to turn on/off support for legacy routes to support older clients. Enabled by default.
• serverMetrics (boolean) - use this option to turn on/off prometheus metrics.
• preHook (function) - this is a hook if you need to provide any middlewares to express before unleash adds any. Express app instance is injected as first argument.
• preRouterHook (function) - use this to register custom express middlewares before the unleash specific routers are added. This is typically how you would register custom middlewares to handle authentication.
• secret (string) - set this when you want to secure unleash. Used to encrypt the user session.
• adminAuthentication (string) - use this when implementing custom admin authentication securing-unleash. Possible values are:
  • none - will disable authentication altogether
  • unsecure - (default) will use simple cookie based authentication. UI will require the user to specify an email in order to use unleash.
  • custom - use this when you implement your own custom authentication logic.

3. Docker

You can also use the hosted docker image to start the Unleash server

docker run -d -e DATABASE_URL=postgres://user:pass@10.200.221.11:5432/unleash unleashorg/unleash-server

How do I configure the log output?

By default, unleash uses log4js to log important information. It is possible to swap out the logger provider (only when using Unleash programmatically). This enables filtering of log levels and easy redirection of output streams.

What is a logger provider?

A logger provider is a function which takes the name of a logger and returns a logger implementation. For instance, the following code snippet shows how a logger provider for the global console object could be written:

function consoleLoggerProvider(name) {
  // do something with the name
  return {
    debug: console.log,
    info: console.log,
    warn: console.log,
    error: console.error,
  };
}

The logger interface with its debug, info, warn and error methods expects format string support as seen in debug or the JavaScript console object. Many commonly used logging implementations cover this API, e.g., bunyan, pino or winston.

How do I set a logger provider?

Custom logger providers need to be set before requiring the unleash-server module. The following example shows how this can be done:

// first configure the logger provider
const unleashLogger = require('unleash-server/logger');
unleashLogger.setLoggerProvider(consoleLoggerProvider);

// then require unleash-server and continue as normal
const unleash = require('unleash-server');