![xwlt1 ewallet go xwlt1 ewallet go](https://getfreebies.my/wp-content/uploads/2021/07/209386055_4149714768448050_849191374670862539_n-768x768.jpg)
![xwlt1 ewallet go xwlt1 ewallet go](https://ezcab.com.my/wp-content/uploads/2020/12/We_accept_banner_021220-1080x380.png)
These are SDKs for integrating with the OmiseGO eWallet Server.
![xwlt1 ewallet go xwlt1 ewallet go](https://1.bp.blogspot.com/-4VNoRh0SFAQ/XeTiS0zRCBI/AAAAAAABQFA/gEcl8lC8TLwQ8zAToXvQAUiHwZecEzm-wCNcBGAsYHQ/s1600/photo6278349555565177194.jpg)
Please note that OmiseGO eWallet Staging tracks development release and there might be API differences from the stable release. In case you want to explore the API documentation without installing the OmiseGO eWallet Server, you may use our OmiseGO eWallet Staging. /api/client/docs.ui for Client API, used by client apps to create transaction on behalf of user, user's settings, etc./api/admin/docs.ui for Admin API, used by server apps to manage tokens, accounts, transactions, global settings, etc.You may review the API documentation at the following locations in the OmiseGO eWallet Server setup. 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. It is recommended to take a look at the documentation of the OmiseGO eWallet Server you are running. DocumentationĪll documentations can found in the docs directory. config gcs_credentials "gcs configuration". 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.
#XWLT1 EWALLET GO UPDATE#
These commands will update the configuration key (see also settings documentation) in the database. docker run -it -rm omisego/ewallet:latest config (Docker).docker-compose run -rm ewallet config (Docker-Compose).seed -settings will seed the application settings for the OmiseGO eWallet Server.seed -e2e will seed a data for end-to-end testing.seed -sample will seed a sample data suitable for evaluating OmiseGO eWallet Server.The seed command may be configured to seed with other kind of seed data: If seed is run without arguments, the command will seed initial data for production environment. These commands create the initial data in the database. docker run -it -rm omisego/ewallet:latest seed (Docker).docker-compose run -rm ewallet seed (Docker-Compose).This command is expected to be run every time you have upgraded the version of OmiseGO eWallet Suite.
#XWLT1 EWALLET GO UPGRADE#
These commands create the database if not already created, or upgrade them if necessary. docker run -it -rm omisego/ewallet:latest initdb (Docker).docker-compose run -rm ewallet initdb (Docker-Compose).In case of bare metal, see also bare metal installation instruction.In case of Docker, use docker run -it -rm omisego/ewallet.In case of Docker-Compose, use docker-compose run -rm ewallet.The way to invoke these commands depend on the installation method you choose. Commandsĭocker image entrypoint is configured to recognize most commands that are used during normal operations. Encountered a problem during the installation? See the Setup Troubleshooting Guide.įor other platforms or a more advanced setup, see alternative installation below.