Build an application that allows users to manage Sidekiq services. We'll call this application "Sidekicker", but you can name it anything you want.
Sidekiq is a background processing service that can be integrated into Rails applications. Basically, Sidekiq can make Rails applications much faster and more efficient. When you're maintaining many applications that use Sidekiq, it's cumbersome to manage each Sidekiq instance separately. Therefore we'll build the Sidekicker app, which will present a central location to manage Sidekiq services for all the apps that you are maintaining.
We'll assume that all of our applications will be built using Amazon's AWS servers, so the Sidekicker app will need a way to communicate with AWS, and run Sidekiq services on Amazon servers.
- As a user I should be able to sign in and out of Sidekicker.
- As a user I should be able to see a list of currently active Sidekiq services.
- As a user I should be able to restart one or many Sidekiq service(s).
- As a user I should be able to see the current Sidekiq jobs processed across all Sidekiq services.
- Of course we'll need to integrate Sidekiq into the Sidekicker app.
- We'll use MongoDB as our backend to this application.
- Use Mongoid in order to make working with a MangoDB backend easier. Mongoid provides an ActiveRecord-esque API for querying a MongoDB database.
- Use Fog to make speaking with Amazon servers easier.
Follow the requirements and use the resources detailed in this checkpoint. Build an app that allows its users to manage Sidekiq services across many Amazon hosted Rails applications.
Remember that you can develop your own requirements for Sidekicker. This checkpoint lays out the bare minimum for basic functionality, but you should customize your app with your own ideas too.