jimmyjose-dev/hours

Time registration that doesn't suck

Hours

Hours is a dead simple project based time tracking application that we use for internal time-tracking. It allows users to register how many hours they've worked on a project with a certain category (think design, software development, testing for software teams) and add any tag they like to it. This gives us a lot of insight on how we spend our time on different projects.

It looks like this:

Roadmap

As we're using Hours we're constantly thinking of ways to improve it and there are a couple of features that we'd like to implement:

• Billable/non billable hours
• Better reporting
• Exporting data
• Mobile apps

System Dependencies

• Ruby 2.1.0 (install with rbenv)
• Rubygems
• Bundler (gem install bundler)
• PostgreSQL
• qmake (brew install qt) or read extensive instructions here
• memcached (brew install memcached, an older version ships with OSX)(optional)

Getting Started

This repository comes equipped with a self-setup script:

% ./bin/setup

For local mail support you need to enter your gmail address and password in .env file.

GMAIL_USERNAME="[email protected]"
GMAIL_PASSWORD="password"

After setting up, you can run the application using foreman:

% foreman start

Since we're using subdomains to point to accounts, you can't run the app on localhost. If you have pow set up, it will be automatically configured by the setup script, otherwise you need to point apache/nginx to the port foreman is running the app on (7000 by default). With pow the app will run on http://hours.dev

In order to activate caching in development you can add CACHE_DEVELOPMENT="anything" to your .env. Make sure to run $ memcached when you do need this.

Guidelines

• Pull requests are welcome! If you aren't able to contribute code please open an issue on Github.
• Write specs!
• Develop features on dedicated feature branches, feel free to open a PR while it's still WIP
• Please adhere to the Thoughtbot ruby styleguide
• All code and commit messages should be in English
• Commit messages are written in the imperative with a short, descriptive title. Good => Return a 204 when updating a question, bad => Changed http response or I updated the http response on the update action in the QuestionController because we're not showing any data there. The first line should always be 50 characters or less and that it should be followed by a blank line.

License

Hours is distributed under the MIT license.