Different cache setting required for css + image assets
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 22
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
idk what to set for this, but this makes developing with changing CSS very difficult (especially since development CSS might not have hashed filename to bust the cache). Seems like it’s meant for production.
Contributor guide
No contributing guide indexed for this repository
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 with the referenced default.conf.tpl section at lines 63-66 and inspect how caching is currently configured for CSS and image assets. Determine the intended development and production behavior, then verify that the configuration supports changing development CSS without hashed filenames defeating updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100