|
I’m with Daniel. The node that downloads the files from the Chef server is in the best position to know the required end of line character. Julian’s point supports
mine nicely. How can I tell Git or my editor to always use <LF> or <CR><LF> when some cookbooks (and therefore templates) might be used on more than one platform? Perhaps Opscode could add a tag to templates that flags chef-client to make the file’s end of
line characters conform? @Tensibai I too use gvim and can control the line endings. However, what set this off was the use of a community cookbook. I
could edit the community cookbook to change the line endings, but I shouldn’t have to. From: Tensibai [mailto:
FWIW: I think the file format and encoding is the responsability of the cookbook/template writer. There's plenty of editors allowing to set the file encoding and line endings the way you wish. I think about gvim and notepad++ for thoose I actually use for this purpose. At least it must be an option as magically converting a file at rendering could become confusing. I think about rendering config files on a server to push them toward a switch later, you may wish to keep the encoding of the file even if it is not the server base encoding. Tensibai Le 2013-11-07 04:40, Daniel Condomitti a écrit :
|
Archive powered by MHonArc 2.6.16.