FrankDW I would probably use some kind of job queue mechanism that supports time-based jobs, like you schedule a job for 5 minutes. Then if a new thing comes in, you can delete the scheduled job, if it hasn't been performed yet.
I vaguely remember there was a way to set up rspec to do certain things for certain types of tests... for example, always set a request header for controller specs... anyone remember how to do this?
IGnorAND yeah. I used to just run it directly on the dev machine, but now I run it thru docker on the dev machine.
IGnorAND well, I'll usually still have the dev libraries installed for the database, because whatever db adapter usually needs those to compile, but the running database would just be in docker.
pretty much, I set up a `docker-compose.yml` file for each of my projects, and have ALL the external dependencies live in there, like db, redis, elasticsearch, nginx, whatever.
AgelZ: okay, last time I'm gonna say this. Please tell me what the issue is. I don't want to read through your entire project codebase. Tell me what the issue is so I can figure out where to start.
I'm signing out for tonight, but I will be around tomorrow, if you have some specific questions
AgelZ: sure. Sinatra might be a little confusing at first too, so you might want to search for "Ruby Test Driven Development Tutorial" as well just to get familiar with testing Ruby
sorry, I'm a little confused here.. you have geolocation data in session store, but need it in default_scope?
can you just make a "fake" default_scope in the controller, where you do like @user = User.find(x).with_geo(lat: lat, long: long) and then basically return a user with a scope attached to that object, and use @user everywhere?