You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated on #351, paths on left side of colon are relative to Git working directory and not of the syncroot path. Why is that?
I guess the 'scopes' feature are meant to upload always the same code to different servers.
But I have a different usecase. I have different directories that need to be uploaded to different servers. This is becoming very common with git monorepos. I could not find a tool better suited to me than git-ftp, it knows the difference between commints and only uploads changed files.
But I kind of need to have different '.git-ftp-include' files for each scope. The solution I have come up with is the following shell script file:
Because the include file takes files from the root instead of the syncroot, I have to copy my folder from syncroot to root. I also need to change my include file according to the scope.
I guess an easy way to solve this would be to add an configuration to the scope specifying what include file to use, instead of using the generic '.git-ftp-include'.
Environment
Please copy the output of the following commands.
echo"$SHELL"
uname -a
git-ftp version
# output:
/bin/bash
Linux RAFAEL-PC 4.4.0-18362-Microsoft #836-Microsoft Mon May 05 16:04:00 PST 2020
x86_64 x86_64 x86_64 GNU/Linux
git-ftp version 1.6.0
The text was updated successfully, but these errors were encountered:
I'd really love to contribute, but I'm not experienced with shell scripts, I only know the basics 🤦
Maybe it would also be necessary to add an option to make the paths in the include file to the left of colon to be relative to the syncroot? Because changing that behaviour without an option would be a breaking change... But I don't think it make much sense to upload from working directory instead of syncroot...
Enhancement
As stated on #351, paths on left side of colon are relative to Git working directory and not of the syncroot path. Why is that?
I guess the 'scopes' feature are meant to upload always the same code to different servers.
But I have a different usecase. I have different directories that need to be uploaded to different servers. This is becoming very common with git monorepos. I could not find a tool better suited to me than git-ftp, it knows the difference between commints and only uploads changed files.
But I kind of need to have different '.git-ftp-include' files for each scope. The solution I have come up with is the following shell script file:
Because the include file takes files from the root instead of the syncroot, I have to copy my folder from syncroot to root. I also need to change my include file according to the scope.
I guess an easy way to solve this would be to add an configuration to the scope specifying what include file to use, instead of using the generic '.git-ftp-include'.
Environment
Please copy the output of the following commands.
The text was updated successfully, but these errors were encountered: