| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #2 | 15791 | tjuricek | Removing very old p4ws branch | ||
| #1 | 13266 | tjuricek |
Reorganized depot to avoid stream/main in path. This may be re-imported. |
||
| //guest/tjuricek/p4ws/stream/main/p4_phoenix_services/clients/ruby/phoenix_services_client/Gemfile | |||||
| #2 | 13188 | tjuricek |
Added Docker configuration for notification services, and phoenix services, also, opened up most ports to the host by default. The current configuration is now working first for a setup of "development mode" environments, anticipating that each service will use the private internal network for most services. That way, you can selectively run things, say, in your OS X environment, and other things in the docker cluster. It can make your debugging a little easier. When more automation is available, we'll find a way to describe how to handle this in different ways. |
||
| #1 | 13180 | tjuricek |
Phoenix notification services, client API, including new phoenix_updater This is an interim 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. |
||