I suggest you ...

← Service Improvement

Tracked deletions in git should be synced with the server upon deployment

Currently when using the git deployment feature, if you delete a previously tracked file and push this change to the server it doesn't delete the file from the server.

This means you're left with lots of legacy files that are no longer needed, and your repo is no longer in sync with your server files.

This can cause issues if you ever wanted to push changes back from the server to git as it would then track the previously deleted files and re-add them to the sever!

I'd assume this to be expected behaviour but there might be a reason if anyone wants to shed some light?

Thanks, Harry.

4 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Harry Francis shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Sjors commented  ·   ·  Flag as inappropriate

    In my case it looks there is problem with renaming or moving files. If i rename files of move files to a different folder i think the remove will not get updated properly

  • Justus Grunow commented  ·   ·  Flag as inappropriate

    I love Cloudways, but we absolutely need the ability for files deleted in Git to be also removed from the server. I run a flat-file CMS on Cloudways, and manage the entire site via Github. This behavior means that when I delete a page via Git, the page is not deleted from the server. I have to SSH in and manually delete the pages.

  • Justin Moh commented  ·   ·  Flag as inappropriate

    Hi, this issue is very easy to be replicated -- might not the same, but close enough.

    1. Deploy with your git repository
    2. Push a commit
    3. Pull the repository on Cloudways
    4. `git reset --hard xxxxxxx` (you accidentally pushed credentials) and push the new commit
    5. Pull the repository on Cloudways
    6. Look in to the file content of that modified file : doomed.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Hello,

    Thanks for looking into my submission.

    What you have described is what I'm hoping to do. When I was working on a site recently I found this wasn't the case. I made a support ticket about it to confirm it was expected behaviour and they said it was and that I could make a feature request here.

    Maybe it could have been a permissions issue on my end but I'm confused as support said this was intended.

    Thanks, Harry.

Service Improvement: Server Configuration Improvements

Categories

Feedback and Knowledge Base

(thinking…)