Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Forever documentation about .foreverignore
See original GitHub issueI got this error:
error: Could not read .foreverignore file.
error: ENOENT, open '/var/www/ilanbiala.com/public_html/.foreverignore'
but I can’t find docs about .foreverignore. What goes in there?
Issue Analytics
- State:
- Created 9 years ago
- Comments:17 (3 by maintainers)
Top Results From Across the Web
forever node.js - watch directory for file changes - Stack Overflow
foreverignore and list everything that you do not want forever to watch. This basically tells forever to ignore changes to these files and...
Read more >forever - npm
A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever). Latest version: 4.0.3, last published: a year ago....
Read more >Forever documentation about .foreverignore - langdev
Forever documentation about .foreverignore. 랑재 2015. 5. 7. 16:47. 증상: Nodejs 서버를 돌리면서 forever를 사용 중 인데. 디플로이용으로 잘쓰고 있던 서버 ...
Read more >forever | Yarn - Package Manager
Important: This documentation covers modern versions of Yarn. For 1.x docs, see classic.yarnpkg.com. Yarn.
Read more >using forever and syntax | NodeBB
I need forvere to ignore some files and I noticed a couple of references to a .foreverignore file you can use to do...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve not added anything to my .foreverignore file so cannot comment on the correct format, but I was getting this error until I; a) Created an empty .foreverignore in my project root b) Used the --watchDirectory option and set it to my project root i.e.
forever -w --watchDirectory ./ myscript.jsObviously change the watch dir as required.
I got it working. Add .foreverignore in the directory you’re watching, then add
.log
to the file, or whatever file pattern you’d like to ignore. Thats it. I’m using this now