include: - ruby.ruby22 - perforce.web-services.user-gemsets # This will create wrappers available at the folder path: p4_project_services-gemset: cmd.run: - name: source /usr/local/rvm/scripts/rvm; rvm gemset create p4_project_services - unless: source /usr/local/rvm/scripts/rvm; rvm alias list | grep p4_project_services - user: webservices - shell: /bin/bash - require: - sls: perforce.web-services.user-gemsets # Before we do anything else, we really need bundler to handle doing the # majority of system setup. p4_project_services bundler: cmd.run: - name: {{ pillar['p4_project_services.ruby.wrappers'] }}/gem install bundler - unless: source /usr/local/rvm/scripts/rvm; rvm alias list | grep bundle - user: webservices - require: - cmd: p4_project_services-gemset
# | 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 | 13768 | tjuricek |
Fixing the version of bundler to 1.8.9. The recent changes to 1.9.x don't seem to work smoothly with RVM - 'rake install' (a task defined by bundler) seems to shell out to the 'gem' command, which doesn't appear to be configured quite right when launched via an RVM wrapper script. |
||
#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 | 13517 | tjuricek |
Revised Salt hierarchy to allow for CD clustering. Now, there are two main salt environments: 'build' and 'eval'. The 'eval' environment can be configured for testing or development by setting the Grain 'dev_pillar: True' or 'test_pillar: True'. The test modes may need a bit more effort to figure out exactly where I'll put the .deb files. The dev box passes p4_web_api tests. |
||
#1 | 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. |