Skip to content
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

Use a memory cache store in development #4007

Merged
merged 1 commit into from
Jun 15, 2020
Merged

Use a memory cache store in development #4007

merged 1 commit into from
Jun 15, 2020

Conversation

javierm
Copy link
Member

@javierm javierm commented May 10, 2020

References

Background

In commit 574133a we configured the development to use Dalli to cache pages. However, cache is usually disabled in the development environment.

When we upgraded to Rails 5 in commit eb36b7e, we configured the development environment to enable caching (using a memory store) when a certain file is present, and to disable it when it's not. This configuration makes more sense IMHO, and it was being overwritten by the one previously mentioned.

Objectives

  • Allow caching in the development environment without memcached
  • Get rid of the DalliError: No server available error message

In commit 574133a we configured the development to use Dalli to cache
pages. However, cache is usually disabled in the development
environment.

When we upgraded to Rails 5 in commit eb36b7e, we configured the
development environment to enable caching (using a memory store) when a
certain file is present, and to disable it when it's not. This
configuration makes more sense IMHO, and it was being overwritten by the
one previously mentioned.

After this change, using memcached is no longer required in the
development environment and the `DalliError: No server available` error
message is gone.
@javierm javierm merged commit 129fbb5 into master Jun 15, 2020
@javierm javierm deleted the development_cache branch June 15, 2020 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants