I deployed the official material-ui ssr example to Microsoft Azure, it doesn't work. I also deployed it to Heroku, it still doesn't work. On my local machine and on codesandbox , everything looks good. I don't know what I'm missing.
UPDATE
You can choose docker when you create webapp services. I think it will help you solve the issue.
PRIVIOUS
I think this project has some bug in it.
You can raise a support on azure portal, or submit a issue on github.
I have try to use many ways to deploy ssr project.
Continuous deployment to Azure App Service [Failed]
FTP, then run start command. [Failed]
Use VSCode to publish. [Failed]
Paste zip file into kudu. [Failed]
After all the attempts, I guess that a certain command of the project may take up a lot of resources, so this project has potential bugs, and the azure team can assist in finding the cause of the deployment failure.
This is my error msg.
Related
I have a Wordle-esque app that I want to deploy using Azure. Repo here. It is a fork from a popular open-source project, and I can also locally build and run the game. Locally, it runs perfectly.
I am trying to use Azure App Services to deploy it, using a Github Action. All the Actions pass, and the App can be successfully built. However, when I try to view the deployment here the only error I am receiving is
You do not have permission to view this directory or page.
Since it runs locally, and it pass its github action build, I do not know how to proceed here. I have tried restarting the app, and changing the resources I am using to host it, but that does not work. Some other answers seem to suggest the problem is about it not finding index.html, but I can access that through https://shetland-wordle.azurewebsites.net/public/index.html and the page is blank.
If i look under wwwroot/ in the Azure debugger I see the following file structure:
Any help would be appreciated
turns out it was something strange with package.json. I needed to change the path to my react scripts:
"start": "node_modules/react-scripts/bin/react-scripts.js start"
Not sure if its good practise to do this, but it works now
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.
I"m trying to deploy a simple Node.JS app to Heroku from Cloud9, and I can't seem to be able to find the "Deploy" button to deploy it to Heroku. Is this feature present on Heroku?
http://imgur.com/mrEvDz1
In the current Cloud9 release we do not have a UI for deployment yet, but we're going to add those features soon. They have been flaky at times and we really want to offer things that work.
Until then, I'd recommend using the deployment tools straight from the command line in the Terminal - see our documentation site for details: https://docs.c9.io/deploying_via_cli.html .
Regarding Heroku, deploying via the terminal is not too difficult, although I would have preferred not to disappoint you. All steps are explained in the link below, you can start at step 3 because the Heroku tool belt should already be installed.
Refer: https://devcenter.heroku.com/articles/quickstart
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