Use Fastly-Rails Gem

[Zhao-Andy]

Is your feature request related to a problem? Please describe.
We have an custom version of clearing our cache through Fastly, that involves URLs. The fastly-rails gem could streamline our process and make things smoother.

Describe the solution you'd like
We decide on whether or not to use the fastly-rails gem.

[benhalpern]

We do use Fastly-Rails gem already, but we don't follow it's exact prescribed cache clearing solution, mostly because we couldn't get it to work at first.

I'm in favor of continuing to look into improvements here.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 7 days. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If this issue still requires attention, please respond with a comment. Happy Coding!

[Zhao-Andy]

Believe we still want to do this.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 7 days. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If this issue still requires attention, please respond with a comment. Happy Coding!

[rhymes]

still an issue

[rhymes]

This should help A Guide to Caching Your Rails Application With Fastly

[stale]

Thanks for contributing to this issue. As it has been 180 days since the last activity, we are automatically closing the issue in 30 days. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If this issue still requires attention, please respond with a comment. Happy Coding!

[rhymes]

I believe we should keep this open. With everything we're learning now, through #4744 and #5543 we'll eventually use fastly and fastly-rails more effectively, instead of manually calling endpoints with HTTParty

[rhymes]

Adding these resources about Fastly here, they might help who wants to tackle this:

• Getting started with surrogate keys

• Purging API cache with surrogate keys

• Checking cache

• Understanding cache HIT and MISS headers with shielded services

• fastly-ruby

• fastly-rails

[tannakartikey]

@rhymes fastly-rails gem is deprecated. I am trying to give Rails update(#2879) a try and stumbled upon your comments there:
fastly/fastly-rails#87 (comment)

Should we change the title of this issue to "Use fastly gem" and then actually use it? fastly gem is compatible with Rails 6.

[rhymes]

Hi @tannakartikey, thanks for the update!

Indeed is deprecated. We're in the process of removing the fastly-rails gem, see:

• Copy set_cache_control_headers from fastly-rails #7070
• Copy set_surrogate_key_header from fastly-rails #7108
• Update manual Fastly header assignments #7119
• Copy ActiveRecord methods from fastly-rails #7145
• Remove FastlyRails #7155

I'd suggest you hit the pause button on this, at least until we've finished the process and updated fastly-ruby and verified everything works in production.

I'm going close this in the meantime as we're going in the opposite direction :)

If you don't mind I'm going to reserve the Rails 6 upgrade path issue to the DEV team as we've other blockers likely and we need to verify that everything works with our custom defaults (we don't use all the defaults of Rails 5.2 for example).

Let me know if you have questions!