Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
NoAgendaDashboard.com site source
JavaScript Ruby
branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
app
config
db
doc
lib
public
script
spec
vendor/plugins
.gitignore
.rspec
.rvmrc
.travis.yml
Gemfile
Gemfile.lock
LICENSE
Procfile
README.rdoc
Rakefile
config.ru

README.rdoc

NoAgenda Attack Vector Dashboard

This is the complete source for the http://noagendadashboard.com web application.

Some technologies it demonstrates in combination:

The NoAgenda Show?

No Agenda is a podcast hosted by Adam Curry and John C. Dvorak twice a week on Thursday and Sunday in the morning. The show deconstructs the news and media memes. It accepts no advertisers, instead being directly supported and promoted by the listeners.

Translation/Internationalisation

Currently the site is all in English, but we can support other languages if someone can help with the translations.

All the translatable text is in the file: noagenda_dashboard/blob/master/config/locales/en.yml

To provide a tranlsation for a given language, just grab a copy of this file, rename is <language-code>.yml, translate all the definitions and send it/push it back. Please keep it in UTF-8 character set though.

Enabling Twitter Notifications

The site will tweet when new shows are loaded. It requires twitter oauth settings to be set with these environment variables:

  • navd_consumer_key

  • navd_consumer_secret

  • navd_token

  • navd_token_secret

Set these locally as normal environment variables e.g.:

$ export navd_consumer_key="the_consumer_key_from_twitter"

To set these on heroku:

$ heroku config:add navd_consumer_key=".." navd_consumer_secret=".." navd_token=".." navd_token_secret=".."

Contributing

Yes please! If you have any ideas, or can help with design, development or translation, you are most welcome.

If you are familiar with the github process, we're good to go:

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet

  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it

  • Fork the project

  • Start a feature/bugfix branch

  • Do your stuff (adding tests where appropriate)

  • Commit and push until you are happy with your contribution

  • Send me a pull request on github.

Something went wrong with that request. Please try again.