-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add editoast --no-cache
option
#7419
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one. By the way, should this option be activated by default (simplifying the developer onboarding?). No cache means no Redis to deploy locally, so it might be interesting.
I don't want to enable it by default. Using docker compose we have a redis that runs easily. Disabling the cache makes the tile server very slow. Which is not good behavior, even for developers. |
38f51c9
to
b556827
Compare
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #7419 +/- ##
============================================
- Coverage 29.39% 29.38% -0.01%
Complexity 2011 2011
============================================
Files 1171 1171
Lines 145240 145246 +6
Branches 2822 2822
============================================
- Hits 42691 42682 -9
- Misses 100885 100900 +15
Partials 1664 1664
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This option allows to disable caching. It's useful for developers working on core and using editoast endpoints.
b556827
to
020ee06
Compare
This option allows to disable caching.
It's useful for developers working on core and using editoast endpoints.