listen ENV['HWS_PORT'] || 9000
worker_processes ENV['HWS_WORKERS'] || 8
stdout_path ENV['HWS_STDOUT_PATH'] if ENV.key?('HWS_STDOUT_PATH')
stderr_path ENV['HWS_STDERR_PATH'] if ENV.key?('HWS_STDERR_PATH')
pid ENV['UNICORN_PID'] if ENV.key?('UNICORN_PID') | # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 15741 | ptomiak | Branch HWS for my use. | ||
| //guest/perforce_software/helix-web-services/main/source/helix_web_services/config/unicorn.rb | |||||
| #1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
| //guest/perforce_software/helix-web-services/main/helix_web_services/config/unicorn.rb | |||||
| #3 | 15587 | tjuricek |
Add 'rake test' top level command to handle executing tests against the local source tree. This may be embellished with some additional configuration to, say, run tests against a remote server. |
||
| #2 | 14053 | tjuricek | Fix references to environment vars | ||
| #1 | 13799 | tjuricek |
Start with branch specs hosting in a new monolithic 'helix web services' project. Converting from a microservice to a monolithic architecture due to resource constraints at getting a deployable system running. Additionally, since it's not expected that people will upgrade often, the major benefit of microservices - being able to add services individually without affecting others - is not really a major benefit. The Ruby SDK will be consolidated into a single 'helix web services client' project. It may end up being distributed via Rubygems. This only runs branch specs at the moment. I want to get a CD pipeline setup for the monolithic server before revising more methods. |
||