Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Allow to call the files even when you are in another instance atm | Joas Schilling | 2016-10-06 | 1 | -1/+1 |
| | | | | Signed-off-by: Joas Schilling <coding@schilljs.com> | ||||
* | Move OCS Provider to PSR-4 namespace | Joas Schilling | 2016-05-19 | 2 | -96/+1 |
| | |||||
* | Fix formatting of response | Lukas Reschke | 2016-02-25 | 1 | -2/+4 |
| | | | | The elements are expected to be within a `service` array as per specification. | ||||
* | Reference v2 in the provider list | Lukas Reschke | 2015-10-13 | 1 | -10/+10 |
| | |||||
* | Add endpoint with list of OCS providers | Lukas Reschke | 2015-06-27 | 2 | -0/+126 |
This adds a OCS provider list at `ocs-provider/` to enable a somewhat autodiscovery of services. In the moment it is not possible for applications to add own entries and it is basically hard-coded in the controller. I'm aware that this is not an optimal solution and I'm happy for any pragmatic input that won't pollute our public API too much. (and is not a big super hack, this is already hacky enough ;-)) That said, I'd consider it as a first step also feasible to go with this somewhat hard-coded list and see if this gets adopted... |