include: - ruby.ruby22 - perforce.web-services.user-gemsets # This will create wrappers available at the folder path: p4_phoenix_services-gemset: cmd.run: - name: source /usr/local/rvm/scripts/rvm; rvm use 2.2.2; rvm gemset create p4_phoenix_services - unless: source /usr/local/rvm/scripts/rvm; rvm use 2.2.2; rvm alias list | grep p4_phoenix_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_phoenix_services bundler: cmd.run: - name: {{ pillar['p4_phoenix_services.ruby.wrappers'] }}/gem install bundler --version 1.8.9 - unless: {{ pillar['p4_phoenix_services.ruby.wrappers'] }}/gem list | grep bundle - user: webservices - require: - cmd: p4_phoenix_services-gemset
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#3 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#2 | 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. |
||
#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). |