option for private files analogous to dotfiles

Open
  • Is something wrong?
#110 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
backend

Research direction

The issue names no file or test; begin by locating the existing dotfiles option and the entry point that handles file permissions. Done means an option analogous to dotfiles can ignore files lacking world-readable permission, with the behavior and Windows compatibility clarified.

Written by the indexing model from the issue text.

Description

awaiting more info

I don't know if this would even work because I don't know if Windows has something like this, but I'm wondering if you would be open to adding an option (or accepting a PR) to handle private files (files that do not have world-readable) in the same way that dotfiles is handled.

A public file or directory is typically mode 644 or 755

A private file or directory is typically mode 400 or 500

My suggestion is that an option like privatefiles: 'ignore' would treat any file lacking world-readable permission (the o of ugo does not have 4) the same as dotfiles: 'ignore' is currently treated.

Dominant language
JavaScript
Stars
1.4k
Forks
240
Avg merge
3d 21h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from expressjs/serve-static

All issues in expressjs/serve-static

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.