valitydev/party-management
14
0
Fork 0
mirror of https://github.com/valitydev/party-management.git synced 2024-11-06 01:05:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
357 Commits 9 Branches 0 Tags 938 KiB
Erlang 99.2%
Makefile 0.4%
Dockerfile 0.3%
bbbeae5006
Go to file
Артем bbbeae5006
TD-330: Fix - Add merge and calc of turnover limit to withdrawal terms (#22)
2022-07-13 17:13:43 +03:00
.github/workflows TD-222: Reuse valitydev/action-deploy-docker@v2 (#21) 2022-07-12 11:09:19 +03:00
apps TD-330: Fix - Add merge and calc of turnover limit to withdrawal terms (#22) 2022-07-13 17:13:43 +03:00
config TD-262: Move from shumpune to accounter (#15) 2022-04-08 01:32:50 +03:00
test/machinegun changed workdir according a wetkitty:service-erlang.sls.tpl (#1) 2021-06-18 15:02:32 +03:00
.dockerignore TD-128: Add CI, Makefile, Dockerfile and docker-compose.yaml (#2) 2022-02-07 11:17:17 +03:00
.env TD-330: Bump damsel (#20) 2022-07-01 13:40:47 +03:00
.gitignore TD-128: Add CI, Makefile, Dockerfile and docker-compose.yaml (#2) 2022-02-07 11:17:17 +03:00
compose.yml TD-262: Move from shumpune to accounter (#15) 2022-04-08 01:32:50 +03:00
Dockerfile TD-226: Remove UserInfo-based auth (#13) 2022-04-05 14:51:12 +03:00
Dockerfile.dev TD-226: Remove UserInfo-based auth (#13) 2022-04-05 14:51:12 +03:00
elvis.config TD-330: Bump damsel (#20) 2022-07-01 13:40:47 +03:00
LICENSE Update file(s) from valitydev/.github 2022-02-22 07:25:13 +00:00
Makefile TD-128: Add CI, Makefile, Dockerfile and docker-compose.yaml (#2) 2022-02-07 11:17:17 +03:00
README.md Build and push images w/ GH action (#1) 2021-12-08 19:35:32 +03:00
rebar.config TD-330: Bump damsel (#20) 2022-07-01 13:40:47 +03:00
rebar.lock TD-330: Bump damsel (#20) 2022-07-01 13:40:47 +03:00
TODO.md HG-48: Switch to the new stateproc protocol (#14) 2016-08-11 15:52:58 +00:00

README.md

Party Management

Managing parties involved in payment processing.

Building

We widelly use Thrift to define RPC protocols. So it needs to have our Thrift compiler in PATH to build this service. The recommended way to achieve this is by using our build image.