9d46f1fbd7
* TD-572. impelementation get_limit * TD-572: add test for get_limits * TD-572: fix formatting * TD-572: add test for exception * TD-572: change limits output format * TD-572: fix spec * TD-572: fix naming, add test --------- Co-authored-by: anatoliy.losev <losto@nix> |
||
|---|---|---|
| .github | ||
| apps | ||
| config | ||
| doc | ||
| test/machinegun | ||
| .dockerignore | ||
| .editorconfig | ||
| .env | ||
| .gitignore | ||
| compose.yaml | ||
| Dockerfile | ||
| Dockerfile.dev | ||
| elvis.config | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| rebar.config | ||
| rebar.lock | ||
| renovate.json | ||
| TODO.md | ||
Hellgate
Core logic service for payment states processing.
Building
To build the project, run the following command:
$ make compile
Running
To enter the Erlang shell with the project running, run the following command:
$ make rebar-shell
Development environment
Run in a docker container
You can run any of the tasks defined in the Makefile from inside of a docker container (defined in Dockerfile.dev) by prefixing the task name with wc-. To successfully build the dev container you need Docker BuildKit enabled. This can be accomplished by either installing docker-buildx locally, or exporting the DOCKER_BUILDKIT=1 environment variable.
Example
- This command will run the
compiletask in a docker container:
$ make wc-compile
Run in a docker-compose environment
Similarly, you can run any of the tasks defined in the Makefile from inside of a docker-compose environment (defined in docker-compose.yaml) by prefixing the task name with wdeps-. To successfully build the dev container you need Docker BuildKit enabled (see Run in a docker container section). It may also be necessary to export a COMPOSE_DOCKER_CLI_BUILD=1 environment variable for docker-compose container builds to work properly.
Example
- This command will run the
testtask in a docker-compose environment:
$ make wdeps-test
Documentation
@TODO Please write a couple of words about what your project does and how it does it.