| Name | Modified | Size |
|---|---|---|
| .. | ||
| phoenix_services_client |
| 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 |
| 13635 | tjuricek | Exploring modular web applications with Sinatra. If the app has fairly unique content p...er page, Sinatra works really well actually. (Mostly because it's a thin layer over Rack.) Sharing anything though, basically means implementing a module or base class and implementing it everywhere. An added benefit is that these applications could be used in Rails apps as well. I'd probably think hard about this, because Rails tends to be a resource hog. Here's an example config.ru I used for running against the dev system: require 'pms' app = Pms::App.new Pms::Login.settings.p4_web_api_url = http://172.16.100.20/p4_web_api/v1 ProjectApp.settings.phoenix_services_url = http://172.16.100.20/p4_phoenix_services/v1 app.settings.static = :true app.settings.public_folder = File.absolute_path('../../ui/pms', __FILE__) puts "public_folder is #{app.settings.public_folder}" run app « |
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 |
| 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 |
| 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 |