Hi there, you're probably wondering how you got here. Well no worries, I can for sure tell you that you don't even need Github anymore to view your issues, cause this application is all you need!

Steps to get up and running:

1. Docker. I recommend the desktop app: https://www.docker.com/products/docker-desktop
2. Docker compose: https://docs.docker.com/compose/install/ (This should come with the Docker desktop app on MacOS)
3. Make sure you're in the application directory and run docker-compose up
4. After everything starts up, you may visit 0.0.0.0:3000 but it should now say database is missing. Let's remedy that. Please run docker-compose run web rake db:create db:migrate, it may take a hot minute to complete.
5. Refresh 0.0.0.0:3000 in your browser and now you're good to go!

1. Make sure docker-compose up is all up and running (See above for details)
2. Go inside the application container docker exec -t issue-viewer_web_1 sh
3. RAILS_ENV=test rspec

• Webhooks can be set up for creating and updating repositories and issues for a github user, to supplement fetching. This can alleviate some synchronicity issues cause issues and repo data and acccess are subject to changing. Syncing data with a remote source of truth is always a challenge.
• Data fetching from Github should be done in background jobs so it doesn't hold up web requests
• Instead of storing auth_token on User, that could be abstracted into another table so a user can hold many tokens
• Devise can be used to handle more methods of authenticating, as well as permissions, if further types of users need to be added
• auth_token stored on User should be encrypted. We should not be storing super sensitive data as-is, even in the database
• Add mechanism for refreshing expired tokens
• Add mechanism for rate limiting (Github allows 5000 calls per hour for authenticated requests)
• Add handling for Github user deleting permissions to the client after they've authenticated
• Response caching (w/redis), for example issues may change often, but repos should not typically change that often
• Adding Rack::Attack protection for API endpoints against spam
• Repositories and Issue data should not change across Github users. The current system can be further abstracted with joins tables so we don't need to duplicate the same data shared amongst different users.

• Better/prettier UX/UI Design :(
• More spinners and indicators for user feedback while things load
• Move login mechanics into the react app
• Further filters on the serializer to return only just the required attributes
• Favicon, and other metadata for SEO
• Translations
• Breadcrumbs and proper navigation bar
• Going back in browser when deep inside issues pagination pages only returns to first page instead of previous page