| Name | Modified | Size |
|---|---|---|
| .. | ||
| p4_web_services_auth | ||
| p4_web_services_auth.rb | 10 years ago |
| Change | User | Description | Committed |
|---|---|---|---|
| 13972 | tjuricek | Removing old microservice implementations. The system is now mostly a monolith. Eventua...lly there will be a websocket service. « |
10 years ago |
| 13481 | tjuricek | Tests for the p4 web api and p4 project services now pass against a development setup both... in and out of the docker cluster. Note that configuration *has not* been finalized, so conventions to dealing with development vs production need to be organized a bit. « |
10 years ago |
| 13474 | tjuricek | Corrected regressions that broke the API and Project services specs. | 10 years ago |
| 13470 | tjuricek | Phoenix notification services, client API, including new phoenix_updater This is an int...erim commit containing a first pass implementation of the phoenix_updater. Notably missing parts: - The Qt API doesn't yet actually interact with the phoenix_updater - The phoenix_services web service doesn't filter out notifications I *may* end up creating another web application *just* to filter out notifications, since this may end up taking up a lot of background workers. « |
10 years ago |
| 13441 | tjuricek | As an interim step, allow the application/json Accept type to return the p4d ticket for th...e server. In the future, there will likely be an adjustment to the POST request to store a separate host we attempt to generate a ticket for. Right now, these are host unlocked tickets, and not the production solution. « |
10 years ago |
| 13412 | tjuricek | Initial version of the web-services mainline. This is a collection of several projects,... that will likely often get released together, though many of them may not always be relevant. See the README for more information. « |
10 years ago |