Use Cloudflare CDN for static assets
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 104
- Forks
- 205
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 63
Description
Description of the issue 📄
During a past incident I learned that Rails is serving up static assets, which is completely unnecessary. We already have the domain set up with Cloudflare, so we may as well use their CDN and save some load on the Rails app.
Screenshots 📷
Go look at the log files ;)
Steps to fix 🛠
https://www.bigbinary.com/blog/using-cloudflare-as-cdn-for-rails-applications
To do 📋
- Claim this issue (comment below, or assign yourself if you are part of the codebar org)
- Fork and clone the repository
- Update the relevant files. Follow the steps to fix section in this issue.
- Commit your changes as one commit. Use the title of this issue as your commit message
- Submit a pull request
- Mention this issue in the PR description by including it's number
- Have your pull request reviewed & merged by a codebar team member
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Rails asset-serving log files and the linked Cloudflare CDN guide. Locate the relevant configuration or deployment files, then verify that static assets are delivered through the CDN rather than the Rails application and that the change works in the deployed environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- cloud, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100