So I'm trying to deploy a Laravel app to azure and it worked fine at the start. In this project, I need to use SOAP so I included the SoapWrapper package in my Laravel app. When however I try to deploy it to Azure after adding SoapWrapper, I get the following message:
This says that the soap module and the PHP version are not compatible. However, when I ssh into my Linux server and grab the PHP API I get the same one as the one of the modules:
I am kind of lost on how to fix this and why this happens.
Also, the path
/opt/php/7.3.27/ini/php.ini
which is stated on the first picture doesn't exist in my linux server.
Any help or suggestions?
Related
I have NextJS app with SSG. This functionality was added recently and according to it I should do next-export after next-build to get static files. But after appearing in 9.4 of Incremental Static Regeneration I need to keep server on by npm-start command (in my case I use custom server file with next-express functionality). It works good locally and It works good when I get artifact from Azure. But It doesn't work globally when it will be deployed finally. Help please
Through my attempts, I found that it is impossible to install globally or use next in Azure Web App. That is, it cannot be deployed through Github.Deploying using other methods such as FTP cannot run successfully. It should be related to the azure node environment.
But the method provided in this post says that it can be processed by adding web.config. I think it should be useful and helpful to you. Please read it carefully and try it.
You also can read this document, maybe it useful to you.
I've created two pipelines: build and release for Nodejs app.
Here is the link to nodejs app repo: azure web service
Here is the tasks for build pipeline:
Here is the wwwroot folder structure:
So it is look like all required files are present.
Despite that, I'm constantly receiving:
You do not have permission to view this directory or page
I've tried to add web.config file, but it did not help.
I have front end application on same App service Plan and it works, so it is no way that I have bad service plan.
Do you have any suggestions?
Thanks a lot.
I was able to deploy my service only after using nodejs-docs-hello-world starter.
It is looks like web.config is a required file, btw, still did not find any meaningfull documentation for web.config.
Make sure your azure nodejs env support your js syntax (import from ...), in other case use webpack or typescript.
I'have found App Service Editor very helpful if you want to debug your code errors. See section Output.
I had a problem also with nodejs version, despite the fact I choosed node 12 tls during web app creation, I have noticed that my app used node 6 under the hood. So I changed default nodejs version to 10. See here how to do it
Also, I want to thank #Jason Pan for his help.
Using this official Azure tutorial, I was able to perform all the steps until the step Browse to the app where when I browse to the app using http://myNodeJsTestApp.azurewebsites.net I get the following error:
The page cannot be displayed because an internal server error has occurred.
Please note that using same URL that tutorial asks us to use in step Set Node.js runtime of the tutorial, I was able to successfully display the exact same screen shown in that section. So the error is occurring after I got to the step Browse to the app further down. I'm using NodeJS version 8.12.0.
If you follow exactly the steps and don't modify the sample code, the only fault causing Internal server error is the node version 8.12.0.
Azure server doesn't install Node.js of all existing versions, go https://yourwebappname.scm.azurewebsites.net/api/diagnostics/runtime to check available ones.
I recommend to use 8.11.1 LTS version as the tutorial suggests, or you can choose 10.6.0 the latest on Azure.
I am just trying to upgrade my Azure Mobile Service(AMS) to Mobile app service with the help of documentation link provided here.
I have successfully migrated my Mobile service with the help of button provided on portal. After that I also installed node server on my local machine and installed following node package -
npm i -g azure-mobile-apps-compatibility
I have also obtained my Azure Mobile Service script files. Following is my folder hierarchy of Scripts folder -
Now here in this step I am stuck. I am trying to Scaffold the new Azure Mobile Apps backend with the help of following Node command -
scaffold-mobile-app scripts out
When I executed above command, I am getting following errors in node command prompt -
After looking at the errors I thought that there is some problem with my municipality api files. So I also tried removing my municipality.js and permissions.js file. After that I re executed the scaffolding command. But it again gave me the following error -
I did some research to resolve this error. But I did not get any relevant help in that context. Can someone help/ guide me so that I can proceed further in this upgrade activity?
There are several tutorials on Azure showing how to deploy a node.js server using git. Azure has a nifty feature where you can link a Dropbox folder to an Azure web site for very simple deployments. Works awesome for websites, but I was hoping it might work for node.js deployments as well.
It doesn't seem to work- the deployment process goes fine, but navigating to the URL of the node.js deployment produces this error:
The page cannot be displayed because an internal server error has occurred.
Anyone know if it's possible to deploy a node.js server to Windows Azure via Dropbox?
Many thanks-
UPDATE-
Just ran through the deployment logs and found this line:
The package.json file is not present.
The node.js application will run with the default node.js version 0.6.20.
Perhaps that it explains my problem?
from the console and folder type "npm init" to generate package.json