Skip to content

Allow different git-ftp-include for each scope #583

Open
@rhengles

Description

@rhengles

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:

rm .git-ftp-include

cp .git-ftp-include-back .git-ftp-include

mv ./backend/api/vendor ./vendor

git ftp push -v -s back

mv ./vendor ./backend/api/vendor

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or improvement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions