environ variable for forecastio key
extract current_forecast from application_controller
going to require a forecast model
forecast_spec and forecast model
users_controller_spec tests for welcome forecast, other spec cleanup
require lat/lon for user model
gets forecast from user parameters on signup
Forecasts are made when a user signs up, using their lat/long, and the current time. Isn't called again, and no messaging or ui to see the forecasts.
amalgamate random /workers into app/workers
so that is how you test resque, with resque_spec gem
configure redis, configure Resque in separate initializers
spec working for welcome_email and current_forecast queues
resque-scheduler gem
resque-scheduler connected to ui, can shedule tasks via resque_schedule.yml
scheduling seems to work, not tested
mailer tests
consolidate workers into two files, which requires manually requiring in controller
scheduled forecasts can be sent
Can now send a daily email to a user with their latest forecast, which can also be scheduled
Includes the ability to send a scheduled email