| Name | Modified | Size |
|---|---|---|
| .. | ||
| lib | ||
| spec | ||
| docker-compose.yml | 10 years ago | |
| Dockerfile | 10 years ago | |
| Gemfile | 10 years ago | |
| LICENSE.txt | 10 years ago | |
| phoenix_updater.gemspec | 10 years ago | |
| Rakefile | 10 years ago | |
| README.md | 10 years ago | |
| run | 10 years ago | |
| run.sh | 10 years ago | |
| .gitignore | 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 |
| 13535 | tjuricek | Add notification_services to deployment, and reconfigure build step to exec bash. The e...xecution bit doesn't seem to stay set on config/bash.sh The notification_services service doesn't have advanced tests just yet. « |
10 years ago |
| 13534 | tjuricek | Remove automatically generated license files and unused run.sh files. | 10 years ago |
| 13528 | tjuricek | Moved rack and app server configuration to be managed via Salt. Also, only using a sing...le value "url" to configure how the p4_project_services instance references the p4_web_api. And, removing the Docker setup, since that won't work for a production system. « |
10 years ago |
| 13487 | tjuricek | Pushing host, port, and URL configuration into docker-compose.yml consistently. All oth...er configuration will be figured out by a separate system later. P4WEBAPI-51 « |
10 years ago |
| 13478 | tjuricek | Added Docker configuration for notification services, and phoenix services, also, opened u...p 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. « |
10 years ago |
| 13471 | tjuricek |
Define some JSON messages for Qt API's websocket interaction. Not tested... yet. |
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 |