# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#1 | 13530 | tjuricek |
Add p4_phoenix_services package and Salt configuration for deployment. This uncovered a couple of issues from the C++ API during it's conversion to C++03. So, in a nutshell, most operations, except for notifications, appear to be working (well, using Vagrant machines). |
||
//guest/perforce_software/helix-web-services/main/p4_phoenix_services/p4_phoenix_services/config/puma.rb | |||||
#2 | 13487 | tjuricek |
Pushing host, port, and URL configuration into docker-compose.yml consistently. All other configuration will be figured out by a separate system later. P4WEBAPI-51 |
||
#1 | 13478 | 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. |