Usage: schema-mapper-server [OPTION]...

Start a schema mapper server

  -p, --project		Chooses the strategy for project storage, expects subargs
  -e, --expose		Exposes the store via given strategy in subarg, can be rest, websocket or admin. multiple --expose's can be added
  -d, --driver		Adds storage driver given by strategy in subarg, can be elasticsearch, postgresql or leveldb. multiple --driver's can be added
  -v, --verbose		Log to stdout

How to subargs:

Subargs are used for passing options to project storage, drivers and exposers.
It looks like this: [ <strategy> --extra options ]

How to add my own driver?

For now the only way to use your own driver, exposer or project storage is by using the node API.
Please submit a pull request to schema-mapper-store to let us know about your driver and we will happily add it in a new release.

Examples:

# Start a server with elasticsearch, postgresql and leveldb storage drivers, exposing the Admin interface, a REST API and Websocket
schema-mapper-server \
  --project [ file --path /schema-mapper/project ] \
  --expose [ websocket --port 7000 ] \
  --expose [ rest --port 7100 ] \
  --expose [ admin --port 7200 ] \
  --driver [ elasticsearch --host http://localhost:9200 ] \
  --driver [ postgresql --host localhost --user postgres --password schemamapper ] \
  --driver [ leveldb --path /schema-mapper/level ]

# Same as previous example but instead of passing arguments, passing environment variables
STORE_PROJECT_STRATEGY=file \
STORE_PROJECT_FILE_PATH=/schema-mapper/project \
STORE_EXPOSE_STRATEGIES=websocket,rest,admin \
STORE_EXPOSE_WEBSOCKET_PORT=7000 \
STORE_EXPOSE_REST_PORT=7100 \
STORE_EXPOSE_ADMIN_PORT=7200 \
STORE_DRIVER_STRATEGIES=elasticsearch,postgresql,leveldb \
STORE_DRIVER_ELASTICSEARCH_HOST=http://localhost:9200 \
STORE_DRIVER_POSTGRESQL_HOST=localhost \
STORE_DRIVER_POSTGRESQL_USER=postgres \
STORE_DRIVER_POSTGRESQL_PASSWORD=schemamapper \
STORE_DRIVER_LEVELDB_PATH=/schema-mapper/level \
schema-mapper-server