# coding: utf-8 lib = File.expand_path('../lib', __FILE__) $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib) require 'phoenix_updater/version' Gem::Specification.new do |spec| spec.name = 'p4_phoenix_updater' spec.version = PhoenixUpdater::VERSION spec.authors = ['Tristan Juricek'] spec.email = ['tjuricek@perforce.com'] # if spec.respond_to?(:metadata) # spec.metadata['allowed_push_host'] = 'TODO: Set to 'http://mygemserver.com' to prevent pushes to rubygems.org, or delete to allow pushes to any server.' # end spec.summary = %q{Websocket Server for Phoenix Project Notifications} spec.description = %q{Uses EM-WebSocket to provide outgoing messages to Phoenix clients.} spec.homepage = 'http://perforce.com' spec.license = 'MIT' spec.files = Dir.glob('lib/**/*') + %w( .gitignore LICENSE.txt phoenix_updater.gemspec Rakefile README.md ) spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) } spec.require_paths = ['lib'] spec.add_development_dependency 'bundler', '~> 1.7' spec.add_development_dependency 'rake', '~> 10.0' spec.add_runtime_dependency 'em-websocket', '~> 0.5' spec.add_runtime_dependency 'thread_safe', '~> 0.3' end
# | 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 | 13535 | tjuricek |
Add notification_services to deployment, and reconfigure build step to exec bash. The execution bit doesn't seem to stay set on config/bash.sh The notification_services service doesn't have advanced tests just yet. |
||
#1 | 13470 | tjuricek |
Phoenix notification services, client API, including new phoenix_updater This is an interim commit containing a first pass implementation of the phoenix_updater. Notably missing parts: - The Qt API doesn't yet actually interact with the phoenix_updater - The phoenix_services web service doesn't filter out notifications I *may* end up creating another web application *just* to filter out notifications, since this may end up taking up a lot of background workers. |