Jason Fleetwood-Boldt
Jason Fleetwood-Boldt
why would you want a "liveness and readiness probe" check something fake? If the "liveness and readiness probe" are supposed to hit the real sign in page endpoint, then why...
if you really want a "liveness and readiness probe" just make a hit something served by Middleware (like mount a Rack app) so that it doesn't mess with the Rails...
>> When I am logging in, the session is sometimes lost and I need to re-enter my user and password (I am sure my user and password are correct) and...
>> is this expected behaviour or may be something wrong in the way i have configured the gem? No it is supposed to pick up your session on each request....
``` jobs: build: executor: default steps: - run: name: Force Bundler Version command: | sudo gem update --system echo 'export BUNDLER_VERSION=$(cat Gemfile.lock | tail -1 | tr -d " ")'...
the only purpose of this is to standardize the development process across different paradigms (Importmap, JSBundling, Webpacker, Shakapacker, etc) so that new devs don't have to learn a different way...
we took care of this in our controller code
Yes I was wondering about that. I assume that pull is targeted against 3.1?
I've got a nasty little bug that shows up only in QA environments as well. I actually didn't test production (since my code isn't there yet), but my bug definitely...