55157bfd0e
Some popular applications (for example, Phusion Passenger) leave `*.pid.lock` file(s). For example, when you type `passenger start` with simple express app listening on port 3000, it leaves the following files: * `passenger.3000.pid` (removed when passenger stops) * `passenger.3000.log` * `passenger.3000.pid.lock` While `*pid` and `*.log` are ignored, `*.pid.lock` remains unignored. Phusion Passenger is quite popular, and `*.pid.lock` file should be ignored.
39 lines
589 B
Plaintext
39 lines
589 B
Plaintext
# Logs
|
|
logs
|
|
*.log
|
|
npm-debug.log*
|
|
|
|
# Runtime data
|
|
pids
|
|
*.pid
|
|
*.seed
|
|
*.pid.lock
|
|
|
|
# Directory for instrumented libs generated by jscoverage/JSCover
|
|
lib-cov
|
|
|
|
# Coverage directory used by tools like istanbul
|
|
coverage
|
|
|
|
# nyc test coverage
|
|
.nyc_output
|
|
|
|
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
|
|
.grunt
|
|
|
|
# node-waf configuration
|
|
.lock-wscript
|
|
|
|
# Compiled binary addons (http://nodejs.org/api/addons.html)
|
|
build/Release
|
|
|
|
# Dependency directories
|
|
node_modules
|
|
jspm_packages
|
|
|
|
# Optional npm cache directory
|
|
.npm
|
|
|
|
# Optional REPL history
|
|
.node_repl_history
|