Webapp ARM template, how build MSDeploy zip after deploy

laurent-14 146

Hello,

Till now I have succeeded to make an ARM template for a web app, using the extension MSDeploy (with packageUri zip in an azure blob storage).
Inside the package zip file, I have a create-react-app with all files (package.json, node_modules, src, ...), but without the build folder.

But my problem is that I would like to build the application on the azure web app, in order to load some environment variables from the server app settings (if I build the application locally it cannot see the server app settings).

So here I am -> how in ARM template indicate that after unzip on wwwroot, the application must be build.
(until now I have used the .deployment file with SCM_DO_BUILD_DURING_DEPLOYMENT=true, but that file has no effect using ARM template to create the resource, no build folder is created)

other things I have tried :

putting SCM_DO_BUILD_DURING_DEPLOYMENT in appsettings (it was indicated somewhere to do that for azure functions, but here for webapp seems useless)
try to run the webapp with "npm start" command because this would avoid the building problem, but for create-react-app I have not succeeded to start the webapp server like that yet
looking at new Microsoft.Resources/deploymentScripts, maybe could do the build if it cannot be configured in Microsoft.Web/sites ARM

Thanks for your help,
laurent

ajkuma 22,401 Reputation points Microsoft Employee

2021-02-18T19:40:07.333+00:00

@laurent-14 ,

Typically, SCM_DO_BUILD_DURING_DEPLOYMENT=false - The default for zip deployments is false, and for all other deployment methods is true.
This settings applies to WebApp as well - Kindly check this document -https://github.com/projectkudu/kudu/wiki/Configurable-settings#enabledisable-build-actions
What exactly happens with this settings enabled? Kindly share more details on your requirement, I'll follow-up with you.

To take over the whole deployment script, you can see the approach on customizing the deployment.
Also, see configurable settings that you can leverage based on your needs.

Checkout these docs:
MSDeploy VS. ZipDeploy
Customizing deployments
laurent-14 146 Reputation points

2021-03-01T09:38:57.59+00:00

Thank you for your answer.
I was in day off last week and so have seen your message only now.

Yes I have already tried to put the setting of SCM_DO_BUILD_DURING_DEPLOYMENT at true in the webapp, but nothing build (only if I manually push with vs code)

for information here some line of the webapp config in ARM file :

I will look further in the docs you provided, in particular I did not know the ZipDeploy method, I can give it a try :
I did not use MSDeploy tooling neither vscode to make the zip, I used windows 7 zip but the auto-unzip on webapp is working nice

Note :
seeing building time is a bit long (at end it is for testdrive appsource instances), my last approach was trying to use a webjob that would run a little bash script that would update the environment variable into the react app before running it
-> but here I have another problem i am going to write a second post for this, maybe easizer to solve
ajkuma 22,401 Reputation points Microsoft Employee

2021-03-02T19:10:56.173+00:00

Thanks for the update . Sure, please let me know the ZipDeploy method outcome.
-For the second concern, feel free to open a new thread, one of us (including our MVPs and community, will respond on it soon).
ajkuma 22,401 Reputation points Microsoft Employee

2021-03-05T07:39:48.867+00:00

@laurent-14 , Just following-up to highlight, based on your scenario and has mentioned - ZipDeploy would be better approach. - MSDeploy assumes the package containing already built artifact and do not support the mentioned appSettings.
https://github.com/projectkudu/kudu/wiki/MSDeploy-VS.-ZipDeploy
laurent-14 146 Reputation points

2021-03-05T08:27:36.877+00:00

Hello ajkuma,

Yes I have tried ZipDeploy -> replacing in my ARM web site extension 'MSDeploy' -> 'ZipDeploy', but the deployment was failing (error).

I have not tried further and make it works, because the webjob approach was successful ! got some problems too to be solved (with another microsoft employee help) but it's better in my application not to the suffer of the build delay.

Thanks for your help, i will try later to make ZipDeploy deployment again, because it will likely be usefull to know about for some applications to come.

Best regards,
laurent

PS : how you do to answer to all people ! I have seen there are message every minutes, are you many people to do this and is it your 100% job to help people ?
ajkuma 22,401 Reputation points Microsoft Employee

2021-03-08T20:48:40.28+00:00

@laurent-14 , Thanks for sharing the update and progress on this issue.
Glad to know that the Webjob approach is working fine. (I'll summarize this as an answer post, to help the community find the answer quickly).

P.S:
Appreciate your great positive feedback about the support experience on the Q&A platform. Yes, we have dedicated and active Microsoft engineers delivering the support the Microsoft community expect and deserve.
"Microsoft moderators are Microsoft employees who are part of a support team or a product group. Most or part of their work is to answer questions or help the community." And, also thanks to our Volunteer moderator (and the rest of the community members), who dedicate their time to share their expertise with the community.
laurent-14 146 Reputation points

2021-03-09T13:24:10.51+00:00
To see further, some tests I preformed with ZipDeploy method :

with zip containing only source files + .deployment file containing SCM_DO_BUILD_DURING_DEPLOYMENT=true
=> it has built the node_modules folder with dependencies, but not the build folder after

with zip containing source files + node_modules + .deployment file containing command=npm run build
=> I can see the build has run well (in delployment center) but I cannot find the build folder in wwwroot maybe it creates elsewhere (and so web app doesn't work)

with zip containing only source files + .deployment file with both previous config SCM and command
=> fails : i think it tries to make build folder (the command) before doing the node_modules folder (and so it lack dependencies)

Note : $npm run build command was failing when trying to deploy on F1 free plan app service ("thread was aborted") -> must use B1 plan minimum
laurent-14 146 Reputation points

2021-03-09T13:29:06.61+00:00

I found the builde folder of the 2nd point, it is in :
D:\local\Temp\zipdeploy\extracted\build>

so if I point my start folder to this it should work
ajkuma 22,401 Reputation points Microsoft Employee

2021-03-11T20:59:47.69+00:00

laurent-33, Thanks for sharing your detailed test deploy and the solutions that you tried. It's greatly appreciated.

You may try with local cache as a test -This feature copies your content from the network share to the local disk on the VM. Since the files are local, the load time of node_modules is much faster. The application tries to load most of these files when starting. By default, since your files are stored on the network share on Azure App Service, loading many files can take time.

Kindly see this best practice and troubleshooting guide for node applications
Also, Node.js Modules

Accepted answer

ajkuma 22,401 Reputation points Microsoft Employee

2021-03-09T11:18:19.557+00:00

To benefit the community find the answer quickly, summarizing the comments :

laurent-33 used the webjob to run a bash script for updating the environment variable into the react app before running it.

Alternate approach: via ZipDeploy. MSDeploy assumes the package containing already built artifact and do not support the mentioned appSettings.
https://github.com/projectkudu/kudu/wiki/MSDeploy-VS.-ZipDeploy

@laurent-14 - thanks for sharing the solution that worked for you with the community. It's much appreciated.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Webapp ARM template, how build MSDeploy zip after deploy

0 additional answers