include: - perforce.web-services.p4webapi.god - perforce.web-services.p4webapi.deps # Upstart script that actually launches god, which monitors the unicorn server /etc/init/p4webapi.conf: file: - managed - source: salt://perforce/web-services/p4webapi/p4webapi.conf - user: root - group: root - mode: 644 - template: jinja require: - sls: perforce.web-services.p4webapi.god /var/log/perforce/web-services: file.directory: - user: webservices - group: webservices - mode: 755 - makedirs: True /var/run/perforce/web-services: file.directory: - user: webservices - group: webservices - mode: 755 - makedirs: True
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#5 | 13525 | tjuricek |
Setup God to manage both the p4 web api and p4 project services processes. Apparently, there can only be one true god per machine. |
||
#4 | 13515 | tjuricek |
Initial configuration for the p4_project_services. The tests haven't been run yet, so it's likely missing some more configuration. Using vagrant to even manage these environments may not be our realistic CD premise. I may end up moving some more responsibility into the Salt layer, which would make vSphere automation easier. |
||
#3 | 13513 | tjuricek | Update several files that were missing from the last commit regarding a basic 'test' environment | ||
#2 | 13496 | tjuricek |
Complete and seed the setup of the p4webapi in a development mode. This works against the local development tree for dev environments. |
||
#1 | 13494 | tjuricek | Reorganize salt tree to have a single set of states (probably) organized with different basic minion configurations. |