-
Notifications
You must be signed in to change notification settings - Fork 7
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
General steps idea #2
Comments
HI @mmalka , Do you use getInitialProps, getStaticProps, getSeverSideProps? The purpose of this library is actually to deploy the pages/api folder to azure function apps. I'm working on a new library "nextjs-azure "to handle getInitialProps / getStaticProps / getServerSideProps. If you use anything mentioned above, then I would wait potentially a few weekends for me to release nextjs-azure. If you're just looking to deploy a NextJS fullstack without the above things mentioned then I can definitely help with that as I'm really interested in helping people enjoy the same success we've had hosting on NextJS on azure. If you want to talk on discord my handle is Shanshrew#3112 If you just want some general directional advice I may setup a demo of how to host on "static web apps" which is the Azure service I'd recommend as it gives you zero downtime out of the box, along with frontend/backend and routing support. |
https://github.com/ShanonJackson/nextjs-azure It's fairly far along but still work to be done. I'd recommend using our infra more than happy to help in any way. |
Thank you Jackson, good work. I feel confident so far. :) |
Hello, would you be so kind as to post a general idea of steps a random next.js project would needs in order to be deployed to Azure with your tooling ?
The text was updated successfully, but these errors were encountered: