You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 29, 2019. It is now read-only.
Am I the only one getting this? I doubt it, but it's breaking the elevation climb. And disabling redis fixes it. It'd be easier if everyone had it installed on their environment so we didn't have to depend on redistogo's constraints.
So I'm going to disable redis caching for now?
The other option is just to "cache" the results in mongo, but it really wouldn't scale as well because there'd be nothing to index on.
Disabling caching altogether is a good enough option until we decide to plot elevation, since all we care about now are the start and end elevation points to calculate the climb.
Am I the only one getting this? I doubt it, but it's breaking the elevation climb. And disabling redis fixes it. It'd be easier if everyone had it installed on their environment so we didn't have to depend on redistogo's constraints.
So I'm going to disable redis caching for now?
The other option is just to "cache" the results in mongo, but it really wouldn't scale as well because there'd be nothing to index on.
Disabling caching altogether is a good enough option until we decide to plot elevation, since all we care about now are the start and end elevation points to calculate the climb.