# coding: utf-8 lib = File.expand_path('../lib', __FILE__) $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib) require 'notification_services/version' Gem::Specification.new do |spec| spec.name = 'p4_notification_services' spec.version = NotificationServices::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{Notification Services for Helix Web Services} spec.description = %q{Endpoint from the triggers table for most notifications.} spec.homepage = 'http://perforce.com' spec.license = 'MIT' spec.files = Dir.glob('lib/**/*') + %w( .gitignore .rspec Gemfile LICENSE.txt notification_services.gemspec Rakefile README.md ) spec.bindir = 'exe' spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) } spec.require_paths = ['lib'] spec.add_development_dependency 'bundler', '~> 1.8' spec.add_development_dependency 'p4_web_api_client', '~> 2014.2.0.pre' spec.add_development_dependency 'rake', '~> 10.0' spec.add_runtime_dependency 'p4_web_services_auth', '~> 1.0.0.pre' spec.add_runtime_dependency 'rack', '~> 1.6' spec.add_runtime_dependency 'rack-parser', '~> 0.6' spec.add_runtime_dependency 'sinatra', '~> 1.4' spec.add_runtime_dependency 'sinatra-contrib', '~> 1.4' end
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#7 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#6 | 13689 | tjuricek | Switch from Resque to Sidekiq. | ||
#5 | 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. |
||
#4 | 13478 | tjuricek |
Added Docker configuration for notification services, and phoenix services, also, opened up most ports to the host by default. The current configuration is now working first for a setup of "development mode" environments, anticipating that each service will use the private internal network for most services. That way, you can selectively run things, say, in your OS X environment, and other things in the docker cluster. It can make your debugging a little easier. When more automation is available, we'll find a way to describe how to handle this in different ways. |
||
#3 | 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. |
||
#2 | 13468 | tjuricek | Set up resque worker that will trigger web hooks in the background. | ||
#1 | 13467 | tjuricek | Add a basic notification_services endpoint that can setup a trigger entry and accept basic POST requests. |