An example application that connects to the GitHub REST API and displays users from organizations. Users can then be clicked to retrieve their repositories. Finally, a repository can be clicked and recent commits displayed.
To run locally you will need to install Node.js and grunt.
# Clone the repository.
git clone git://github.com/tbranyen/github-viewer.git
# Change directory into it.
cd github-viewer
# Install the Node dependencies and Bower dependencies.
npm install -q
# Run the server
grunt serverThis is an entirely client-side application, meaning aside from the configured HTTP server and the remote API, there is no server processing. All logic is isolated to JavaScript.
The foundation of the entire application structure and the deployment assets. Along with grunt-bbb the application can be tested locally and built for production with the same tool.
Used for the general layout and View arrangement. Is also used to facilitate re-rendering and collection lists. One single layout is created throughout the lifespan of the application and instead the individual regions are updated.
This is a work-in-progress Backbone plugin to provide a better caching mechanism for Collections. It's used within this application to provide client-side caching in both sessionStorage (persist refresh) and inside memory for faster lookups.
An AMD plugin for loading and inlining optimized Lo-Dash templates. Used to load the templates in a very relative and component-driven way.
Made the design look significantly better than the original. Responsible for the entire UI layer.
This is deployed on a Linode Arch Linux server that runs Nginx. It is served
locally and updated via a git pull and grunt combination.
The configuration looks like:
server {
listen 80;
server_name githubviewer.org;
location / {
root /github-viewer/dist/release;
try_files $uri /index.html;
}
}