2019-08-15 13:33:38 +02:00
2019-08-15 13:33:38 +02:00

hyperreva

Organizational structure

  • using reva as library
  • building services around the library functionalities
  • standalone repos for each service
  • hyperreva as wrapper repository for standalone binary

Suggested repos naming schema:

  • reva-hyper
    • reva-phoenix
    • reva-my-service1
    • reva-my-service2
    • ...

Technical details

Next goals

  • working integration demo
  • minimal drone pipeline for nightly builds
S
Description
No description provided
Readme
342 MiB
Languages
Go 27%
Kotlin 22.8%
Gherkin 20.9%
C++ 14.7%
PHP 7%
Other 7.3%