-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to prevent removing old files #27
Comments
I just tried and was not able to repro. Steps I used:
Result: the new file gets published, and the existing Please try these exact steps. |
Hello,
Try to deploy the same folder with a different file.
In my case the file deployed previously has been removed by the new
deployment.
Thanks
Alessio
Il mar 28 mag 2024, 17:11 David Ebbo ***@***.***> ha scritto:
… I just tried and was not able to repro. Steps I used:
- Create new Azure Web App, which comes with a hostingstart.html
- Download the publish profile
- Use WAWSdeploy to publish a folder with one test file, without
passing any flags
Result: the new file gets published, and the existing hostingstart.html
is still there
Please try these exact steps.
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYJ7P4KJ3KGYWOQE6OCG6DZESNBJAVCNFSM6AAAAABINDGNBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVGQ3TMNRYGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
It does not happen for me. After redeploying with a different file, I still have all the original files. To help isolate, please try again with a fresh site as per my steps above. |
Can you attach the publishSetting used for deploy?
Thanks
Alessio
Il mar 28 mag 2024, 17:49 David Ebbo ***@***.***> ha scritto:
… It does not happen for me. After redeploying with a different file, I
still have all the original files.
To help isolate, please try again with a fresh site as per my steps above.
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYJ7P5S7YWN2LTAPCHRUELZESRSNAVCNFSM6AAAAABINDGNBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVGU4DOMBTGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I used the publishSetting file provided by azure portal.
Do you use the same approach?
Il mar 28 mag 2024, 17:52 Alessio Fabriziani ***@***.***>
ha scritto:
… Can you attach the publishSetting used for deploy?
Thanks
Alessio
Il mar 28 mag 2024, 17:49 David Ebbo ***@***.***> ha
scritto:
> It does not happen for me. After redeploying with a different file, I
> still have all the original files.
>
> To help isolate, please try again with a fresh site as per my steps above.
>
> —
> Reply to this email directly, view it on GitHub
> <#27 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ATYJ7P5S7YWN2LTAPCHRUELZESRSNAVCNFSM6AAAAABINDGNBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVGU4DOMBTGI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Yes, I just downloaded it from the portal. Have you tried with a fresh new app, just to make sure that there is nothing unusual about yours? |
I can't test on a new app unfortunately.
Can you send me some examples about the usage?
Maybe I'm doing something wrong.
Thanks
Il mar 28 mag 2024, 18:21 David Ebbo ***@***.***> ha scritto:
… I used the publishSetting file provided by azure portal. Do you use the
same approach?
Yes, I just downloaded it from the portal.
Have you tried with a fresh new app, just to make sure that there is
nothing unusual about yours?
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYJ7PZILZYVLHWCIG75273ZESVI3AVCNFSM6AAAAABINDGNBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVGY2TQMRRGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Why can't you test on a new app? I just created a free app, and it's ready in a minute at no cost. Usage wise, all I did is run |
I tested with new service app.
First deploy under wwwroot: deployed 10 folders with 10 files inside each
folder.
Second deploy under wwwroot: change only some files inside one
folder...after deploy all other folders removed. Inside the folder with
modified files, only this files are present, all others deleted.
Il mar 28 mag 2024, 19:39 David Ebbo ***@***.***> ha scritto:
… Why can't you test on a new app? I just created a free app, and it's ready
in a minute at no cost.
Usage wise, all I did is run wawsdeploy c:\testfolder
testsite.PublishSettings.
—
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATYJ7P7PKM5KX7I47AZUTMLZES6NNAVCNFSM6AAAAABINDGNBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVG44DQMZUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Strange, I cannot explain it. Note that WAWSDeploy is just a thin wrapper on top of msdeploy.exe. See https://blog.davidebbo.com/2014/03/WAWSDeploy.html for details (and also look at the WAWSDeploy code to see how it calls it). It would be interesting to see if you get the same results when using msdeploy.exe directly. If so, that takes WAWSDeploy out of the equation. |
Hello,
I'm trying to use the tool to deploy code into Azure App Service.
The deploy process works but even if I not declare the /d parameter, the deploy process remove all old files not present in the new deployment.
Any suggestions?
Thanks
Alessio
The text was updated successfully, but these errors were encountered: