+1
now I have to put those files outside the role

I think this should be possible.

Patches would be accepted. Leaving this open.

This is something I was just wishing for the other day too, great to see it! My only comment would be whether it makes more sense to search for these scripts in roles/$role/files instead of a new subdirectory called scripts? In my case I would rather have them in files/ because then you wouldn't have to duplicate file between scripts/ and files/ if you sometimes wanted to use it with copy and sometimes with script...

@mcodd having a separate scripts/ directory is conform files/ and templates/; I used to put regular files in templates/ to (before we had roles), but with roles, it makes more sense to standardize, imho.

Also, I'm not sure what your use case would be to use the same file both as a script resource, and as a files (or even templates) resource?

The same goes for e.g. tasks (or files or templates, ..) you'd use in several roles. As to not duplicate the content, I keep a master file at a certain place, and just symlink them if I have to reuse them.

I would also be inclined to agree with mcodd here, we are copying these
over verbatim, and it keeps from having too many directories (or having to
document things extra)

It should still also fallback to looking in the current spot as I mentioned
if that file didn't exist.

On Sat, May 25, 2013 at 9:52 AM, Serge van Ginderachter <
notifications@github.com> wrote:

@mcodd https://github.com/mcodd having a separate scripts/ directory is
conform files/ and templates/; I used to put regular files in templates/ to
(before we had roles), but with roles, it makes more sense to standardize,
imho.

Also, I'm not sure what your use case would be to use the same file both
as a script resource, and as a files (or even templates) resource?

The same goes for e.g. tasks (or files or templates, ..) you'd use in
several roles. As to not duplicate the content, I keep a pmaster fle at a
certain place, and just symlink them if I have to reuse them.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2969#issuecomment-18447503
.

OK for me.