Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
=========================================================== QIPS NODE AMQP - meant to be run on worker node for QIPS - Pulls Ruote workitems from AMQP Queue - Pulls inputs from either LIMS or from S3 - Uploads outputs back into S3 or LIMS - Sends status updates to RMGR when busy, idle, error, etc - Expects to run scripts that conform to certain spec for output and error processing. see qips-extras! ========================================================== DaemonKit README ================ DaemonKit has generated a skeleton Ruby daemon for you to build on. Please read through this file to ensure you get going quickly. Directories =========== bin/ qips-node-amqp - Stub executable to control your daemon with config/ Environment configuration files lib/ Place for your libraries libexec/ qips-node-amqp.rb - Your daemon code log/ Log files based on the environment name spec/ rspec's home tasks/ Place for rake tasks vendor/ Place for unpacked gems and DaemonKit tmp/ Scratch folder Logging ======= One of the biggest issues with writing daemons are gettign insight into what your daemons are doing. Logging with DaemonKit is simplified as DaemonKit creates log files per environment in log. On all environments except production the log level is set to DEBUG, but you can toggle the log level by sending the running daemon SIGUSR1 and SIGUSR2 signals. SIGUSR1 will toggle between DEBUG and INFO levels, SIGUSR2 will blatantly set the level to DEBUG.