Deploy using a single binary

[felixboehm]

This is part of oCIS Extensions, as a single binary is about to bundle the multiply microservice extensions, and providing good configuration conventions.

• Provide a minimal version to get started #2
• https://github.com/owncloud/ocis-webdav/issues/1
• Provide a minimal version to get started ocis-phoenix#3
• https://github.com/owncloud/ocis-ocs/issues/1

---

[butonic]

ocis-simple is intended to show how to build extensions. As that it will run the full stack, but a self contained set of services that serve as an example for how to write extensions with front and backend parts:

• hello contains the example extension, including a protobuf generated api and a phoenix extension/app?
• phoenix server the web framework. hello adds a ? to it
• konnectd as the openid connect provider for authentication
• devldap as the user backend for konnectd, comes with a few demo users
• gateways and other supporting services from the micro runtime

It will not contain reva or the graph, yet. We will add that to the ocis full sever.

AFAICT we need to decide if we want to run a reverse proxy to hide the different services behind a single entrypoint.

• micro has a built in web proxy that implements routing using a naming convention: https://micro.mu/docs/web.html#routing

[refs]

Why is this issue closed again? There's a PR that can make use of this issue to track. Also, it's part of the backlog. #79

[butonic]

webdav and ocs are currently covered by ocis-reva. moving them into ocis extensions is tracked in

• https://github.com/owncloud/ocis-ocs/issues/10
• https://github.com/owncloud/ocis-webdav/issues/10