GitHub PushEvent at 2014-01-18 22:52:09
Repository: graylog2-rpms
Actor: corey-hammerton
Payload: {"shas":[["06db163c10d6f49d251d8352f49533bdc2591266","a08a07e88d2cfcbb2b470964f31e28187c0533ff@gmail.com","Updating the graylog2 packages to rc.1\n\nChanging the release number in graylog2-server.spec and\ngraylog2-web-interface.spec to the latest release version, which is\nrc.1\n\nBefore building and installing the new packages will need to upgrade\nthe elasticsearch cluster to at least 0.90.10.","coreyh",false],["82928e2025242f687d99c4385d94bb9752149b90","a08a07e88d2cfcbb2b470964f31e28187c0533ff@gmail.com","Merge branch 'master' into issue2","coreyh",true],["f054f83325b1f70bbd7dc3d80210843a55d3956a","a08a07e88d2cfcbb2b470964f31e28187c0533ff@gmail.com","Adding new file log4j-graylog2-server.xml\n\nhttps://github.com/corey-hammerton/graylog2-rpms/issues/2\n\nThe new file is an externalized version of the log4j.xml file that\ncomes pre-packaged in the graylog2-server package. In my experience\nas a sysadmin this is only good for development/test environments,\ncome to production environments the sysadmins need control of the\nlogging. To monitor the application status and send log output to\nthe developers to investigate their code in order to fix any bugs or\nother issues.\n\nWill configure my test graylog2-server instance with a daily\nrolling file appender to write to a self-managed log file instead\nof to the currently configured stdout and redirecting to a file.","coreyh",true]],"size":3,"ref":"refs/heads/issue2","head":"f054f83325b1f70bbd7dc3d80210843a55d3956a"}