lukejacksonn / lukejacksonn/servor
Using pre-gzipped assets
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Hi, we're gzipping files locally to reduce deployment size for some projects.
However, I can't figure out how to test such a build with servor – it just ends up showing me a directory with "index.html.gz" in it (besides others). Is there a flag to allow pre-gzipped content to be served?
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 by inspecting servor's static asset request handling and run the reported build with pre-gzipped files. Done means a build containing index.html.gz and similar assets is served as web content rather than displayed as a directory, with the supported behavior or flag documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100