NEW FEATURE: Option to never delete when syncing

[AliAyub007]

Hello, Is there any option to choose if I don't want to delete the files from server?

If any file is updated it should update but if any file is missing in repo I don't it to be deleted on server.

Plus one more question that how to exclude but not delete from server.

[AliAyub007]

@SamKirkland Any guidance on these questions?

[AliAyub007]

I tested to exclude files but it deleted the files on server even being in exclude list.

[milan-sahana]

when file deleted from git its not deleting from ftp server..

[SamKirkland]

@AliAyub007 I can look into adding a option to never delete files and instead only upload/edit. This is not possible right now and I have no timeline on when I will add this feature.

---

@milan-sahana that sounds like another issue. Can you please make a new issue with more information on what your are seeing & recreation steps.

[Rai-Rai]

+1 for update/edit

[utautattaro]

I want this function too. This is a necessary feature for JAMStack architecture that is updated on a basis.

[Sarah-Alkibsi]

Hi @SamKirkland, is there any update to this feature? Cuz I need it too ^^

I have 2 repositories deployed to one hosting server via FTP. While one app is being deployed to the remote server, it deletes the published folders of the other one.

[afbora]

+1

[heinrich-foto]

+1

[AllinolCP]

+1

[Kacper1263]

+1

[atakilic]

Hey @SamKirkland,

There is a PR that aims to achieve this functionality and it's still waiting to be approved. SamKirkland/ftp-deploy#20. Afterwards I know that some changes have to be applied to this repository. We can contribute to add this functionality to be able to pass new options to ftp-deploy

[luke-cnnect]

Hi @SamKirkland, is there any update to this feature? Cuz I need it too ^^

I have 2 repositories deployed to one hosting server via FTP. While one app is being deployed to the remote server, it deletes the published folders of the other one.

@Sarah-Alkibsi I know this is quite old by now, but I was in the same position and was able to achieve this behaviour by giving two different names to the ftp-deploy-sync-state.json file. You can use the state-name property to define it yourself and then in each repo's yml actions file just name them differently, e.g. "ftp-deploy-sync-state-repo1.json" and "ftp-deploy-sync-state-repo2.json", afterward their states shouldn't interfere and you can deploy two repos to the same remote directory.

Hope it helps if anyone else finds themselves trawling through these issues and PRs xD