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
Description
Mirrored from GitHub
Readme Apache-2.0 936 MiB
Languages
Go 46.9%
Gherkin 37.3%
PHP 12.3%
JavaScript 1.2%
Makefile 0.9%
Other 1.3%