davidtrogers / profit Goto Github PK

• gem install profit
• how you can setup a server to run in a production-like environment
• MIT License
• give props
• more in-code documentation
• fix README code formatting
• 4 major parts - client, server, redis and sinatra app

Some companies will only use gems with a certain license.
The canonical and easy way to check is via the gemspec
via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Bundler now generates gems with a default 'MIT' license. There is even a License Finder
to help companies ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec.
Including a license in your gemspec is a good practice, in any case.

If you need help choosing a license, github has created a license picker tool

How did I find you?

I'm using a script to collect stats on gems, originally looking for download data, but decided to collect licenses too,
and make issues for gemspecs not specifying a license as a public service :)
So far it's going pretty well.
I've written a blog post about it

• add fault tolerance to pending metrics matching, in case the original thread was killed, etc.

• remove puts, replace with a proper logger instance
• improve logging messages when starting up a server

• rack app
• graphs
• stats

• no message exception when you INT the server before a message is sent
• limit the number of messages stored for a particular key
• scope redis keys by profit:metric:some_foo_key
• make client thread safe and metric keys thread aware
• add redis config in server.yml or default to 127.0.0.1:6379

• cli option for server socket type (default to :PULL)
• cli option for client socket type (default to :PUSH)
• cli option for "tcp://*:5556" as binding address
• cli option for "tcp://127.0.0.1:5556" as a connecting address
• add pub/sub, channel selection support

• set up sinatra app with capybara
• tab to different charts
• run the server with profit_app
• hover over a point to see more information, e.g. exact time, time started, etc.
• see information about the code below the graph, e.g. start and stop lines of code, or better, the actual code