jhuttner/how-much-do-i-code — Issue #4: Supporting named configs/file groupings in the API
Author: lcwill
Created: 2012-01-31 06:03:23+00:00
State: open

In adding support for configs on the client-side, you'll be able to arbitrarily group the directories that will be tracked by the daemon and name these groupings. I envision the config file looking something like this:

user.id=lwilliams123
code.tracking.group=Maestro Dev
/usr/local/adnxs/m3api
/usr/local/adnxs/m3ui
/usr/local/adnxs/m3scripts
/usr/local/adnxs/schemas/maestro
code.tracking.group=Personal Projects
/home/lwilliams/git-repos
code.tracking.group=All Dev
/usr/local/adnxs/m3api
/usr/local/adnxs/m3ui
/usr/local/adnxs/m3scripts
/usr/local/adnxs/schemas/maestro
/home/lwilliams/git-repos

The UI could then display these as 3 separate sections (or maybe tabs) in the coding timesheet. In order for that to work, we'll need to add some extra information to each curl request, I'm thinking in the query string:

64.208.137.22:3000/save-event/lwilliams123/1327967595?groups=All%20Dev,Maestro%20Dev

This way, a timestamp could be associated with multiple groups. How does this sound?