mckern / tattletale Goto Github PK

Look at integrating Omniauth for pluggable authentication instead of the unrealistically simple "authentication" in use right now. That'd make it easier to plug multiple authentication backends into place.

The ability to group things together for dashboard rollups would make consuming the metadata around check-in time easier.

Here's some ideas for the sort of things that should be output:

• Check-in history for jobs
  • Maybe some sort of param for specifying how far back to go?
• Job details
  • Any of the metadata about the job itself, like its cron schedule, name, and description
• Approximate run time (subtract the scheduled start from the actual check-in)?

These things are like tribbles, and if left unchecked they will chew up your database like it was grain stores.

• Maybe acts_as_trashable?
• Or maybe use Sidekiq to clean them up in the background?

It's sort of an ad-hoc mess. It works, but it's inelegant.

• Consider adapting Bootstrap?
• At least apply Sass better.

You don't have any. How is that even possible?

This will make it possible to have an unauthenticated rollup endpoint for public jobs.

What you've got now will never cut it. Try these on for size:

• Setup & installation
• Dependencies
• Better usage examples