Jari Bakken 1aca1aac15 Remove spec for EventStore.
This code is well covered anyway, and the test is causing trouble
since emitting the featureCreated event is causing side effects through
other listeners.
2020-02-20 08:30:19 +01:00
2020-02-20 08:30:19 +01:00
2020-02-20 08:30:15 +01:00
2020-02-20 08:30:12 +01:00
2014-09-29 14:50:46 +02:00
2020-02-20 08:30:14 +01:00

unleash-server

Build Status Code Climate Coverage Status Dependency Status devDependency Status

unleash-server is a place to ask for the status of features.

Clients

In order to make use of unleash you will probably need a client implementation.

Known client implementations:

Development

Create a local unleash-db on postgres

$ psql postgres <<SQL
CREATE USER unleash_user WITH PASSWORD 'passord';
CREATE DATABASE unleash;
GRANT ALL PRIVILEGES ON DATABASE unleash to unleash_user;
SQL

Then set DATABASE_URI env var:

export DATABASE_URL=postgres://unleash_user:passord@localhost:5432/unleash

Commands

// Install dependencies
npm install

// Make sure DATABASE_URL is set and run migrations in your local DB
export DATABASE_URL=postgres://unleash_user:passord@localhost:5432/unleash
./node_modules/.bin/db-migrate up

// Start server in dev-mode:
npm run dev

// Admin dashboard
http://localhost:4242

// Feature API:
http://localhost:4242/features

// Execute tests:
npm test


// Run tests with postgres running in docker:
npm run docker-test

Making a schema change

  1. Create migrations/sql/NNN-your-migration-name.up.sql with your change in SQL.
  2. Create migrations/sql/NNN-your-migration-name.down.sql with the rollback of your change in SQL.
  3. Run db-migrate create your-migration-name and edit the generated file to have this line: module.exports = require('../lib/migrationRunner').create('NNN-your-migration-name');
  4. Run db-migrate up.
  5. Generate LB artifact using scripts/generate-liquibase-artifact (TODO: make this internal)
Languages
TypeScript 97.1%
JavaScript 2.2%
Mustache 0.5%