I had a great time working with Hivelocity's VPS again. Get one month of VPS FREE at hivelocityinc.net/3SfVjnB. Use code BYTEGRAD1 at checkout. Learn more about Hivelocity’s VPS: hivelocityinc.net/3s3OcUF
This is amazing. I would love to see a solution for: 1. Using the docker container as a dev container, meaning coding on the container dev server. 2. A solution to rebuild the next app for both dev and production on git push. Making it a replacement for vercel. 3. Any type of autoscaling,
Hello, thank you very much for providing this short and practical content, please make other videos of these practical and interdisciplinary skills (CI/CD) for frontend developers.
Yes CI/CD with build job and some public ENV variable.. How to handle PUBLIC_NEXT_** when the image is created from the CI/CD and env variable are not stored in repo (no env.production in repo)
Excelent content master!! Thank you so much for sharing. It would be really cool if you complement this video with a github action for building the updated image after a master commit, and push it to the VPS. Thank you in advance!
Fantastic content! I've recently done something similar for my own projects: containerizing and setting up CI/CD. It will be interesting for me to see how you continue with CI/CD in this video, and perhaps even more so, how to deploy a web server + database using Docker and Kubernetes while also integrating CI/CD (which is exactly what I'm trying to figure out now LOL).
Thank you @ByteGrad for your videos. Your videos are simple and any engineer can understand what your bring. There is common issue in NextJS and Docker which is access the System Env variables after the build is done in runtime. Please you can check that issue and it is still open for long time. You may share a video about how to solve that issue.
Yes, do we have any solution for that? For the context, I have deployed the dockerized next js on ECS and I'm not able to consume the envs from task definition
Thanks for the video! I completely forgot that I can use the GH registry, that actually solves a small problem I had with where to store the built containers
Great video, just clearing the confusion around EXPOSE keyword on Docker. "The EXPOSE instruction doesn't actually publish the port. It functions as a type of documentation between the person who builds the image and the person who runs the container, about which ports are intended to be published. To publish the port when running the container, use the -p flag on docker run to publish and map one or more ports, or the -P flag to publish all exposed ports and map them to high-order ports."
amazing ...just loved it...could you please make another video adding Github Actions for CI/CD with the current video !....that would be amazing...thanks in advance
In comparison to deploying on Vercel, what features / abilities we will lose if we use docker? I think the obvious ones are serverless functions, edge functions and edge caching. basically we will have only 1 server from 1 geo to serve all of the world
This is great content. I would suggest doing a video about automated workflow with Github Actions like you suggested in the video (and maybe using the Docker Hub this time ?), that would be amazing !
I can finally say that I climbed the steep curve of learning React/Next.js and that's in great part thanks to you. Thank you so much. You're really making a difference as a content creator. Related to this video, Is it possible to set a Python FastAPI backend and a Next.js front end on the same container or would I have to use 2 separate containers?
Highly informative video. Can you please create another Part2 video regarding how to integrate GitHub Repo and using GitHub Actions create a new Docker image and automate the above Workflow. That would be very helpful. Thank you Sir.
Great content. Can you explain the deployment part with GCP? I am not sure since they should have container registry, but how to refer the docker etc.. Very nice content!
Hi Thank you for great content. Would you please also help on how to setup dev branch on sub domain, since the port is same, it always goes to main branch. I am using nginx.
Because Node.js and all node_modules have to be copied to the image. It is supposed to be a standalone container that has all you need to run your application, even denying the necessity of a browser or a NodeJS installation.
Now one needs to add the docker starting of the container automatically at startup. Also in case the container is started and the next server crashes because of an app bug how can you restart the next app ?
hi i have hosted on vps kvm2 Hostinger , but images are braking (next js , typescript, tailwind, mongodb - project) do we need any special settings for nginx or need any url changes i have purchased envato subscription and downloaded images stored them in public folder of next js project working well in localhost but breaking images after getting deployed
can i ask why dont we just git clone our repo after sending our code to github repo , then run that using terminal in the vps, i am not sure why we are using docker is it necessary?
I had a great time working with Hivelocity's VPS again. Get one month of VPS FREE at hivelocityinc.net/3SfVjnB. Use code BYTEGRAD1 at checkout. Learn more about Hivelocity’s VPS: hivelocityinc.net/3s3OcUF
We enjoyed collaborating with you and look forward to more opportunities in the future!
more devops content please, this was really helpful
This is amazing. I would love to see a solution for:
1. Using the docker container as a dev container, meaning coding on the container dev server.
2. A solution to rebuild the next app for both dev and production on git push. Making it a replacement for vercel.
3. Any type of autoscaling,
Check out coolify for #2
2. gha
3. k8s
ive been looking for a solution for 1. as well, pages don't compile for me.
Hello, thank you very much for providing this short and practical content, please make other videos of these practical and interdisciplinary skills (CI/CD) for frontend developers.
Yes, please CI/CD
Definitely pls
Yes CI/CD with build job and some public ENV variable.. How to handle PUBLIC_NEXT_** when the image is created from the CI/CD and env variable are not stored in repo (no env.production in repo)
Few weeks back, i scratched my head for this and you make it look so simple. Thank you so much! Saved!
Dying for a loadbalanced prod tutorial! Thanks subbed!
This is the content I like. Hats off, congrats.
Enjoy!
you're a life-saver!!!! exactly what I needed at work! Cannot thank you enough!!!!!!!!!!!!!
Great efforts indeed! A tutorial of rebuild nextjs app after git push would be cool thing to see on this channel
You don't miss with the videos. Ive never veen happien than since i chose Next JS, abd dockerizing is huge! 🙌🏾
Every time I am stuck you post a video on that certain topic. Good content!
Excelent content master!! Thank you so much for sharing.
It would be really cool if you complement this video with a github action for building the updated image after a master commit, and push it to the VPS.
Thank you in advance!
Fantastic content! I've recently done something similar for my own projects: containerizing and setting up CI/CD. It will be interesting for me to see how you continue with CI/CD in this video, and perhaps even more so, how to deploy a web server + database using Docker and Kubernetes while also integrating CI/CD (which is exactly what I'm trying to figure out now LOL).
Thank you @ByteGrad for your videos. Your videos are simple and any engineer can understand what your bring. There is common issue in NextJS and Docker which is access the System Env variables after the build is done in runtime. Please you can check that issue and it is still open for long time. You may share a video about how to solve that issue.
Yes, do we have any solution for that?
For the context, I have deployed the dockerized next js on ECS and I'm not able to consume the envs from task definition
Thanks for the video! I completely forgot that I can use the GH registry, that actually solves a small problem I had with where to store the built containers
Great video, just clearing the confusion around EXPOSE keyword on Docker.
"The EXPOSE instruction doesn't actually publish the port. It functions as a type of documentation between the person who builds the image and the person who runs the container, about which ports are intended to be published. To publish the port when running the container, use the -p flag on docker run to publish and map one or more ports, or the -P flag to publish all exposed ports and map them to high-order ports."
I recently joined your channel.
I want to tell you that your channel has most advance content than anywhere else.
❤
Continue this with CI/CD next video.
You are a life saver. Thank you
Thanks a lot ! It's working !
Thank you so much
Nice one! you can use automatic port mapping as you exposed the PORT in Dockerfile e.g.( docker run -P "image )
Bro is getting better and better
Great content mate! More of this please. Self hosting ftw!
amazing ...just loved it...could you please make another video adding Github Actions for CI/CD with the current video !....that would be amazing...thanks in advance
Nice and simple and more than that to the point
webdevcody needs this video.
Thanks alot for this short and very helpful tutor
In comparison to deploying on Vercel, what features / abilities we will lose if we use docker?
I think the obvious ones are serverless functions, edge functions and edge caching. basically we will have only 1 server from 1 geo to serve all of the world
exactly what i was looking for!
You're jumping over the "important" bits quite quickly, but it helped a lot - thanks!
This is great content.
I would suggest doing a video about automated workflow with Github Actions like you suggested in the video (and maybe using the Docker Hub this time ?), that would be amazing !
I can finally say that I climbed the steep curve of learning React/Next.js and that's in great part thanks to you. Thank you so much. You're really making a difference as a content creator.
Related to this video, Is it possible to set a Python FastAPI backend and a Next.js front end on the same container or would I have to use 2 separate containers?
Highly informative video. Can you please create another Part2 video regarding how to integrate GitHub Repo and using GitHub Actions create a new Docker image and automate the above Workflow. That would be very helpful. Thank you Sir.
wow, thank you very much, it is appreciated, very good video
Thank you. Thats very useful information.
thank you very much you saved my life
Hi, can you do dockerize with env file in your project too. Thanks you so much
Great content. Can you explain the deployment part with GCP? I am not sure since they should have container registry, but how to refer the docker etc..
Very nice content!
Thanks a lot! You really explained this process perfectly, can we do this with many Node.js apps with different ports and add CI/CD?
Hi Thank you for great content. Would you please also help on how to setup dev branch on sub domain, since the port is same, it always goes to main branch. I am using nginx.
Consider making a video about connecting ssl and domain to this vps.
im using .env file to connect db. how to i pass through it to container with docker compose ?
Is there a way to automate this when you change the code? to build a new docker image and deploy it to the VPS?
Thanks for share this!.. btw can provide de github repository?
Great, can you make one for ci/cd pipelines??
Now, do a kube cluster
Thank you. Do You use a proxy server like nginx?
How to control route and api caching on next js project that not deployed on varcel environment?😢
hey ByteGrad, have you switched to MacOS recently from Windows?
Great.., Please try dockerize Next js with Prisma
Hi, I am still confused why such small project takes above 1GB image size ?, some projects I built almost have 3GB image size
Because Node.js and all node_modules have to be copied to the image. It is supposed to be a standalone container that has all you need to run your application, even denying the necessity of a browser or a NodeJS installation.
It would be cool if you explain at the start what a VPS is and what are the benefits.
So for production you reverse proxy that 3000 port to something else with Nginx or that's something you would do within docker?
Great video. Question: did you not get an error of ECONNREFUSED for the route handler when you did the "build" (npm run build)? How did you avoid it?
Does that mean that I can use websocket protocol & keep connection with backend if it's dockerizable?
pls explain how the docker image size was reduced from 1GB to 170MB? thanks.
Now one needs to add the docker starting of the container automatically at startup. Also in case the container is started and the next server crashes because of an app bug how can you restart the next app ?
nice thank you, please can you do a video about github action.
Nice content
Sir please make JavaScript interview technical coding interview questions videos and great video keep it up
This only works for a single standalone but what about horizontal scaling on docker containers for nextjs ?
What mac do u use?
hi i have hosted on vps kvm2 Hostinger , but images are braking (next js , typescript, tailwind, mongodb - project)
do we need any special settings for nginx or need any url changes
i have purchased envato subscription and downloaded images stored them in public folder of next js project
working well in localhost
but breaking images after getting deployed
Hey, can you make a crash course on micro frontend and module federation please if possible.
What about caching, ISR SSR and so on
a smple next.js app with 5 lines of output is 1gb???
Bonus tip: you can just connect that to a cloudflare tunnel and thus don’t have to worry about connecting your domain properly and ssl certificates
can i ask why dont we just git clone our repo after sending our code to github repo , then run that using terminal in the vps, i am not sure why we are using docker is it necessary?
can you do please an instruction on how Dockerize nest js app????
solid!
hot reloading on dev not working
Eurgh, another video where you don't put the code in a github repo for us to reference :(
Dockerize Nuxt.js & Deploy to VPS
I prefer dockerize only the build
Lmao, another F for mac users.
thx for the info man