Nice to see an upgrade that isn't a MLoC monolith lol
-
-
-
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
That seems like something we can/should fix. If nothing else we should warn if you assign `cache_store` later.
1 reply 0 retweets 0 likes -
Replying to @sgrif @coreyhaines
AFAIK its a known issue, many of the configs we utilize in bootstrap need to be defined in config, or they pick up defaults
1 reply 0 retweets 0 likes -
.. since user initializers run towards the end of bootstrap. Maybe can update docs for that.
2 replies 0 retweets 0 likes
I think a warning would be easy to implement and much more visible than just an offhand mention in the docs
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.