web: build: . command: /notification_services/run.sh ports: - "5004:5004" environment: - BIND_ADDRESS=tcp://0.0.0.0:5004 - NOTIFICATION_SERVICES_HOST=192.168.99.100 - P4_WEB_API_URL=http://p4_web_api:5000 - P4PORT=p4:1666 external_links: - geminabox_geminabox_1:geminabox - p4webapi_web_1:p4_web_api - perforce_p4_1:p4
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#4 | 13528 | tjuricek |
Moved rack and app server configuration to be managed via Salt. Also, only using a single 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. |
||
#3 | 13488 | tjuricek |
Added hsm:startworld and hsm:stopworld tasks to do global starts and stops. This is not without apparent issues. It appears bundler or ruby is pausing before the nginx launch task happens. I'm not sure if there's some kind of resource issue first. P4WEBAPI-49 |
||
#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. |