-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
⚠️ Issue with Azure Deployment Instructions #4891
Comments
@sarah11918 I was thinking about trying out the Azure deployment method, could you assign this to me and I can test it out while I'm at it? |
I have a few other bits I found that may improve the docs as well. I plan to write a blog post, once done I will share here. I would be happy for any of the points to be incorporated into the official docs. |
Here is my post feel free to use as much of it as you wish. https://www.blueboxes.co.uk/deploying-an-astro-website-to-azure-static-web-apps I ran through both using vscode and the azure portal. The current astro guide in this GitHub issue covers everything except the need to set the engine in the package.json though in some places could be a bit clearer. |
@VoxelMC we don't typically assign issues to people, but if an issue is open, that's your sign it's free to take! I've tagged this with |
@blueboxes this looks really useful! We have a community resource section at the end of some CMS guides (example), and I think this would be a good opportunity to add one to our Azure deploy guide. We'd be open to a PR if you want to add your guide! Along with anything other feedback you might have! |
On https://docs.astro.build/en/guides/deploy/microsoft-azure/
You must also set the engine in your
packages.json
as the static website build defaults to node 16 which is not compatible with astrohttps://edi.wang/post/2022/1/27/how-to-specify-nodejs-version-when-building-azure-static-web-app
The text was updated successfully, but these errors were encountered: