Add copy config option

[jerrykal]

Add an option to copy file instead of symlink, e.g.

- link:
    ~/.zshrc:
      copy: true
      path: zshrc

[anishathalye]

Would it be better to just have a separate copy: thing like link: ?

[jerrykal]

That's a good idea.

[sharethewisdom]

Also, options could be added to copy: equivalent to options found in install(1)?

[anishathalye]

Actually, it may be better to have a copy: true option (as @ooJerryLeeoo suggested) rather than a separate copy: task (otherwise, there would be a lot of duplicated logic).

[anishathalye]

As discussed in #221, we couldn't find concrete cases where copy: was necessary. This issue also hasn't received a ton of attention, so perhaps this feature is not needed.

[u1156]

Hi! I think I have a use case for that feature. I want to track my standard Dockerfile and if dotbot links it then docker-compose can't use this symlink as a file. Because docker-compose is strict about working context.
It would be great to be able to instruct dotbot to copy files instead of linking them in some specific cases.

[anishathalye]

I don't use docker-compose, but based on this issue it seems like it does support symlinks (except on Windows)?

[u1156]

I'm on a mac. Symlinks does not seem to work for a Dockerfile.

[anishathalye]

Ah, I see. For now, you can use shell: with a command like cp -u ....

[jmigual]

Hi I found another use case. I have a .gitconfig file that I use both for Windows and Linux. It wouldn't be much of a problem except when signing commits with GPG where Git on Windows requires you to define the gpg.program key if you don't want it to use the incorporated gpg from Git-Bash. So, my idea was to comment the Windows only part of the .gitconfig file, copy the file and uncomment the part if I am on Windows.