Yeah. Thanks. Doing now.
-
-
Replying to @coreyhaines
Nice to see an upgrade that isn't a MLoC monolith lol
1 reply 0 retweets 0 likes -
-
Replying to @coreyhaines @sgrif
Here's the issue https://github.com/rails/rails/issues/29489 …
1 reply 0 retweets 0 likes -
Replying to @coreyhaines @sgrif
Okay, turns that it was in application.rb before, I moved it to an initializer, since rails app:update was overwriting everything there
1 reply 0 retweets 0 likes -
-
Replying to @coreyhaines
Still, it seems odd to me that moving from application.rb to an initializer would break things.
1 reply 0 retweets 0 likes -
Replying to @sgrif
So other railties can access it. I found an old comment about that. Comment on my issue verified.
2 replies 0 retweets 0 likes -
Replying to @coreyhaines
Either way at least it's isolated to exactly that one setting.
1 reply 0 retweets 0 likes -
Replying to @sgrif
Yeah, a warning would be great. It makes sense why it is like that. But, yeah, warning about "This is not setting your cache" :)
2 replies 0 retweets 0 likes
Yeah that's the easy 80/20 solution I think
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.