File and folder removed

[hellohasan]

Hello Sir,

Its a good for deployment, but I am facing some issues. like

I am running a Laravel project under this public directory i have an images folder where my visitor upload their profile photo, but when I deploy a version currently it deletes the old photos and shows my local few user photo only,

2nd one is: when i upload a version as on gitignore I add the vendor files would not upload on git, now when i deploy a version the previous vendor folder is removed, I need to run again the composer install and without that, my site is down.

if it will like its not delete the existing file and folder just replace it with the new file but not delete the existing files and folder.

[hellohasan]

@cloudpanel-io please give me the solution

[lucasvmds]

Hello Sir,

Its a good for deployment, but I am facing some issues. like

I am running a Laravel project under this public directory i have an images folder where my visitor upload their profile photo, but when I deploy a version currently it deletes the old photos and shows my local few user photo only,

2nd one is: when i upload a version as on gitignore I add the vendor files would not upload on git, now when i deploy a version the previous vendor folder is removed, I need to run again the composer install and without that, my site is down.

if it will like its not delete the existing file and folder just replace it with the new file but not delete the existing files and folder.

Hello.
I was passing by and saw your comment.
I don't know if your problem has already been resolved, but this happens due to the nature of dploy in keeping releases/deploys on the server for possible rollback.
So with each deploy it creates a new copy of the application and creates a link to this new copy, which is why you lose the images.

[lucasvmds]

In my opinion, dploy should work as follows:

• Create a command to perform the first deploy or it will automatically recognize whether it is the first deploy or not, thus creating a git clone
• Instead of cloning the entire application throughout the deployment, a git pull could be done, and once finished, make a copy of the current application (you can even read the .gitignore files so as not to copy unnecessary files) and save it in the releases folder , to rollback

[betoco-de]

Hello Sir,

Its a good for deployment, but I am facing some issues. like

I am running a Laravel project under this public directory i have an images folder where my visitor upload their profile photo, but when I deploy a version currently it deletes the old photos and shows my local few user photo only,

2nd one is: when i upload a version as on gitignore I add the vendor files would not upload on git, now when i deploy a version the previous vendor folder is removed, I need to run again the composer install and without that, my site is down.

if it will like its not delete the existing file and folder just replace it with the new file but not delete the existing files and folder.

Hi, I hope you're okay...

Were you able to resolve this issue? The same thing is happening to me.

[adolfoflores]

Hello Sir,
Its a good for deployment, but I am facing some issues. like
I am running a Laravel project under this public directory i have an images folder where my visitor upload their profile photo, but when I deploy a version currently it deletes the old photos and shows my local few user photo only,
2nd one is: when i upload a version as on gitignore I add the vendor files would not upload on git, now when i deploy a version the previous vendor folder is removed, I need to run again the composer install and without that, my site is down.
if it will like its not delete the existing file and folder just replace it with the new file but not delete the existing files and folder.

Hi, I hope you're okay...

Were you able to resolve this issue? The same thing is happening to me.

That’s not how Dploy works—it deploys the entire project from scratch each time, replacing everything. To avoid losing files like images, you might need to store them on a remote server (such as R2 or S3) or find a different deployment solution.