# Installs the p4webapi include: - perforce.web-services.p4webapi.upstart # We actually launch the p4_web_services_auth: cmd.run: - name: {{ pillar['p4webapi.ruby.wrappers'] }}/rake install - user: webservices - unless: {{ pillar['p4webapi.ruby.wrappers'] }}/gem list | grep p4_web_services_auth # Start the service up after making sure everything is installed p4webapi: service: - running - watch: - file: /etc/init/p4webapi.conf - file: /opt/perforce/web-services/conf/p4webapi.god require: - sls: perforce.web-services.p4webapi.upstart - file: /etc/init/p4webapi.conf - file: /opt/perforce/web-services/conf/p4webapi.god - file: /var/log/perforce/web-services - file: /var/run/perforce/web-services - pkg: p4_web_services_auth # In development and testing environments, we use a utility to seed Perforce # data for executing tests. {%if pillar['seed_data'] %} p4util install: cmd.run: - name: {{ pillar['p4webapi.ruby.wrappers'] }}/gem install p4util - user: webservices - unless: {{ pillar['p4webapi.ruby.wrappers'] }}/gem list | grep p4util require: - sls: perforce.web-services.p4webapi.upstart seed data: cmd.run: - name: {{ pillar['p4webapi.ruby.wrappers'] }}/p4util init -p :1666 /home/vagrant/p4ws/p4init - user: webservices require: - cmd: p4util install {% endif %}
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#5 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#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 | 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. |
||
#2 | 13520 | tjuricek |
Created a 'cluster' build procedure that creates an installer on build, and executes the install on a test instance. The main change is to package all gem dependencies via 'vendor/cache' (using the 'bundle package' command). Right now, there appears to be an issue with test data initialization, which may need a revised approach. |
||
#1 | 13512 | tjuricek |
Add 'test-ubuntu12' environment that sets up projects based on "production" packages. Packages are installed from source files that should have been created by the last 'build-ubuntu12' environment. Since the package building process "dirties" up the environment it's better to use a clean system to test package installation. |
||
//guest/perforce_software/helix-web-services/main/salt/srv/perforce/web-services/p4webapi/dev.sls | |||||
#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. |