Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

foreverignore syntax/documentation #417

Closed
EleanorRagone opened this issue May 7, 2013 · 7 comments
Closed

foreverignore syntax/documentation #417

EleanorRagone opened this issue May 7, 2013 · 7 comments
Labels

Comments

@EleanorRagone
Copy link

There doesn't seem to be any documentation on the syntax for a .foreverignore file - where can I get started on this? I'm having some trouble getting it working at all, as it doesn't seem to follow any normal .gitignore-style syntax.

@D1plo1d
Copy link

D1plo1d commented May 7, 2013

It seems like foreverignore has been moved to forever-monitor but I'm having the same issue, no matter what I try it just doesn't work.

https://github.com/nodejitsu/forever-monitor

@D1plo1d
Copy link

D1plo1d commented May 7, 2013

related: #235

@zevero
Copy link

zevero commented Aug 22, 2013

.foreverignore file doesnt work at all for me. Is there still support for it? What can be done?

@Vadorequest
Copy link

You need to restart the forever process each time you change the .foreverignore file.

I also would like to get more information about syntax, such as limit it for .js files.

Edit: Seems like something like this works.

**/.idea/**
**/.git/**

**/.tmp/**
**/views/**
**/assets/**

# Restart only when js files are changed.
!*.js

@ph3nx
Copy link

ph3nx commented Jun 30, 2014

When using *.log it ignores logfiles in the main directory and even in subdirectories.

@indexzero
Copy link
Member

It is just like a .gitignore file.

@wyqydsyq
Copy link

wyqydsyq commented Dec 4, 2014

I'm using forever 0.13.0 (latest on npm at time of writing) and have found out the hard way that .foreverignore behaves barely like a .gitignore file at all. The syntax is different and incredibly confusing to users expecting .gitignore syntax such as:

.tmp/*
.cache/*

You'd expect that would make forever ignore the contents of the .tmp/ and .cache/ folders which it doesn't, this still hasn't been resolved despite #235 having been open since early 2012.

This wouldn't be such a big problem if the correct use of .foreverignore was documented anywhere, which it isn't (unless you count GitHub issues as documentation which I don't)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants