-
Notifications
You must be signed in to change notification settings - Fork 58
Having trouble deploying code in Azure #397
-
Hi Courtney! I'm trying to deploy the code in Azure and having issues publishing. I'm doing it as an experiment to try and build a few new things on top of the already great code, so I need my own sandbox to play around in knowing I can break stuff and it won't matter :)
I'm facing 1 of two issues:
- There is an update Next JS to be compatible with Azure, but when updating with the latest Node version it won't publish
- If I don't update it, the build isn't successful in Azure.
So in general there seems to be some compatibility issue with Azure and the codebase. Any ideas on how to proceed?
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 3 comments 1 reply
-
I suggest forking the repository (making a copy that you control under your account) so that you have your own copy that you can update/mess around with. Changes you make to your forked repository will not affect the main repository here, so you should be free to get it working on your own terms. Updates to the main repository can also be pulled into your forked repository as they happen so that you stay in sync.
I think this is what you are looking for - let me know if you have questions!
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Sorry, I re-read your question and realize maybe I didn't get that right the first time. Are you saying you've already forked it but you simply can't get it build?
In that case:
- What version of Node are you attempting to build the code with?
- What version of NextJS did you attempt to upgrade to?
- Are you getting specific build errors when you attempt to build?
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
Here's the error screen
image (8)
Beta Was this translation helpful? Give feedback.
All reactions
-
Thank you @hluedeke !
@donnelljeffrey-glitch I've never used Azure, so don't know much about it's idiosyncrasies. I googled your error and it seems like maybe you just need to specify the path for the next start script in package.json.
I recently updated the package.json to specify node >=22, because Vercel is dropping support for node v18. That's only on the beta branch currently though.
I would suggest deploying to Vercel, if you are just mucking about since that definitely works. If you want to learn more about Azure, you'll have to do some troubleshooting.
Thanks for giving the project a try and your interest in building on it. I hope you get it working!
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1