@@IntegrationNinjas thank you for this video I did follow this to deploy a nextjs app right for the UI only. Would be excited to see how to dockerize it as well :)
If I want to set up a dev/stage/product environment then in that cases I have to create 3 different ebs app on AWS or in single elastic beanstalk I can handle it? Also how to setup branch specific deployment
The absence of a start script in the package.json file could definitely be a reason for the 502 Bad Gateway error in AWS Elastic Beanstalk. Elastic Beanstalk expects a start script to know how to launch your NodeJS application, and without it, the environment might not know how to correctly start the app, causing the 502 error.
Was looking for this, thanks for sharing 👍
Glad it helped!
Thank you for the video.
What permission policies do I need to have in 13:55?
I think this portion is for AWS access key and id, are you looking for the permission and policies used for elastic beanstalk?
I had successfully deploy my app to aws, seems that permission and policies are not necessary.
Amazing work sir, Please make a video on How to deploy Nextjs full stack app, with github actions and docker on aws ec2
Will try to create asap.
@@IntegrationNinjas thank you for this video I did follow this to deploy a nextjs app right for the UI only. Would be excited to see how to dockerize it as well :)
@@ChristopherMakrides Thanks.
If I want to set up a dev/stage/product environment then in that cases I have to create 3 different ebs app on AWS or in single elastic beanstalk I can handle it? Also how to setup branch specific deployment
How do I structure my project directory when I have separate files for admin, client, and server API to deploy on Elastic Beanstalk?
Iam roles instead of users?
If I have any .ebextensions, would that also work ??
How about how to deploy from a MEAN stack?
I will create a youtube video soon on that
if is work with react app also? thanks
It should. I will create tutorial soon.
i am getting 502 error bad gateway. Is it ok that there is no start script in the package.json?
The absence of a start script in the package.json file could definitely be a reason for the 502 Bad Gateway error in AWS Elastic Beanstalk. Elastic Beanstalk expects a start script to know how to launch your NodeJS application, and without it, the environment might not know how to correctly start the app, causing the 502 error.
@IntegrationNinjas could you please how the package.json should be
अगर हमारे पास 5 वेबसाइट हो तो क्या 5 बार नया इलास्टिक बीनस्टाल क्रिएट करना पड़ेगा...
yes
👏🏻👌🏻