OmiseGO eWallet Server is a server application in OmiseGO eWallet Suite that allows a provider (businesses or individuals) to setup and run their own digital wallet services through a local ledger, and to a decentralized blockchain exchange in the future to form a federated network on the OMG network allowing exchange of any currency into any other in a transparent way.

The quickest way to get OmiseGO eWallet Server running on macOS and Linux is to use Docker-Compose.

1. Install Docker and Docker-Compose

2. Download OmiseGO eWallet Server's docker-compose.yml:

   curl -O -sSL https://raw.githubusercontent.com/omisego/ewallet/master/docker-compose.yml

3. Create docker-compose.override.yml either manually or use this auto-configuration script:

   curl -O -sSL https://raw.githubusercontent.com/omisego/ewallet/master/docker-gen.sh
   chmod +x docker-gen.sh
   ./docker-gen.sh > docker-compose.override.yml
   

4. Initialize the database and start the server:

   docker-compose run --rm ewallet initdb
   docker-compose run --rm ewallet seed
   docker-compose up -d
   

Encountered a problem during the installation? See the Setup Troubleshooting Guide.

For other platforms or a more advanced setup, see alternative installation below.

• Bare metal installation

See Upgrading the eWallet Server.

Docker image entrypoint is configured to recognize most commands that are used during normal operations. The way to invoke these commands depend on the installation method you choose.

• In case of Docker-Compose, use docker-compose run --rm ewallet <command>
• In case of Docker, use docker run -it --rm omisego/ewallet <command>
• In case of bare metal, see also bare metal installation instruction.

For example:

• docker-compose run --rm ewallet initdb (Docker-Compose)
• docker run -it --rm omisego/ewallet:latest initdb (Docker)

These commands create the database if not already created, or upgrade them if necessary. This command is expected to be run every time you have upgraded the version of OmiseGO eWallet Suite.

For example:

• docker-compose run --rm ewallet seed (Docker-Compose)
• docker run -it --rm omisego/ewallet:latest seed (Docker)

These commands create the initial data in the database. If seed is run without arguments, the command will seed initial data for production environment. The seed command may be configured to seed with other kind of seed data:

• seed --sample will seed a sample data suitable for evaluating OmiseGO eWallet Server.
• seed --e2e will seed a data for end-to-end testing.
• seed --settings will seed the application settings for the OmiseGO eWallet Server.

For example:

• docker-compose run --rm ewallet config <key> <value> (Docker-Compose)
• docker run -it --rm omisego/ewallet:latest config <key> <value> (Docker)

These commands will update the configuration key (see also settings documentation) in the database. For some keys which require whitespace, such as gcs_credentials, you can prevent string splitting by putting them in a single or double-quote, e.g. config gcs_credentials "gcs configuration".

All documentations can found in the docs directory. It is recommended to take a look at the documentation of the OmiseGO eWallet Server you are running.

OmiseGO eWallet Server is meant to be run by the provider, and thus API documentation is available in the OmiseGO eWallet Server itself rather than as online documentation. You may review the API documentation at the following locations in the OmiseGO eWallet Server setup.

• /api/admin/docs.ui for Admin API, used by server apps to manage tokens, accounts, transactions, global settings, etc.
• /api/client/docs.ui for Client API, used by client apps to create transaction on behalf of user, user's settings, etc.

In case you want to explore the API documentation without installing the OmiseGO eWallet Server, you may use our OmiseGO eWallet Staging. Please note that OmiseGO eWallet Staging tracks development release and there might be API differences from the stable release.

• Admin API documentation (Swagger JSON, Swagger YAML)
• Client API documentation (Swagger JSON, Swagger YAML)

These are SDKs for integrating with the OmiseGO eWallet Server. For example, to integrate a loyalty point system built on OmiseGO eWallet Server into an existing system.

• Ruby SDK (Sample Server)
• iOS SDK (Sample App)
• Android SDK (Sample App)

It is also possible to run OmiseGO eWallet Server in a standalone mode without needing to integrate into an existing system. These apps demonstrate the capabilities of the OmiseGO eWallet Server as a physical Point-of-Sale server and client.

• iOS PoS for Merchant
• iOS PoS for Customer
• Android PoS for Merchant
• Android PoS for Customer

We are thankful to our community for creating and maintaining these wonderful works that we otherwise could not have done ourselves. If you have ported any part of the OmiseGO eWallet Server to another platform, we will be happy to list them here. Submit us a pull request.

• Alainy/OmiseGo-Go-SDK (Golang)
• block-base/ewallet-js (JavaScript)

Contributing to the OmiseGO eWallet Server can be contributions to the code base, bug reports, feature suggestions or any sort of feedback. Please learn more from our contributing guide.

The OmiseGO eWallet Server team closely monitors the following channels.

• GitHub Issues: Browse or file a report for any bugs found
• Gitter: Discuss features and suggestions in real-time
• Stack Overflow: Search or create a new question with the tag omisego

If you need enterprise support or hosting solutions, please get in touch with us for more details.

The OmiseGO eWallet Server is licensed under the Apache License