Thanks for this. What files exactly will this rule ignore? Is there any documentation or examples in the wild to support this addition? Is the glob necessary?

In fact i am not a pow user at all, one of my coworkers checked his pow configuration files in mistakenly.

I do at least know about two files :

• .powconfig
• .powenv

As i do not use personally this server, i do not know exactly how it works, only know that these files can be added in the project repository to change project specific configuration (i.e. the gems & ruby installation paths)

Do you think it would be better to ignore these two specific files only ?

Yes, it's better to avoid overly general rules if they aren't necessary. I'm reluctant to add these without confirmation that it's sensible in the common case to ignore them. Would you mind doing a little research into the docs or the examples which your colleague checked in to see if these files are user/site-specific (if so then that would be good enough reason to add the rule here), or if there is some other obvious reason they aren't useful to other collaborators?

Hi,

I could find these resources, first the .powenv : http://pow.cx/manual.html#section_2.2 is used to set site specific environment vars.
Then the following gem also adds the .powenv to the gitignore (https://github.com/RailsApps/rails_apps_composer/blob/master/recipes/git.rb#L8)

Since i couldn't find any references to the .powconfig file being used in the application directory (it is normally in ~/.powconfig), i'll assume it was my coworker's mistake and take it out of the PR.

Thanks for the clarification, and yes it looks like it's all site-specific content in general, so this seems sensible. 🎉