Next.js deployed with Docker. Does it make sense?

To try the app: docker run -p 3000:3000 francescoxx/nextapp

0:00 intro
11:15 Push the image on Docker hub
14:00 Does it make sense? Considerations
15:55 LiveCycle extension test @getlivecycle
17:52: Final considerations

Join this channel to get access to perks:

[francescociulla]

0:00 intro
1:05 Next.js app
2:22 Dockerize a NExt.js application
11:15 Push the image on Docker hub
14:00 Does it make sense? Considerations
15:55 LiveCycle extension test
17:52: Final considerations

[pradumnasaraf]

Awesome awesome video. I agree with you. If you have multiple services, then Docker makes more sense with Next.js. But, Docker will be super helpful if you are developing a Next.js app locally.

Also, thank you for using and featuring the Livecycle Docker Extension.

[getlivecycle]

Thanks for the shout out, Francesco 🙏

[Arsy]

brilliant video, well explained and a unique way of presenting this material!

[ramdasvk]

Docker crash course was simply wow. Keep up the good work m, Francesco🔥

[SavaScript]

One thing I tend to do is install NextJS and create my NextJS app *within a Docker container*, instead of within the host. This way I can create my app without installing NodeJS on my host machine.

Also, spot the cameo at 2:22 😅

[johnaroj]

very awesome tutorial. can you explain why we use ouput:standalone in the docker?

[alexdin]

This video doesn't have the quantity of likes that deserve.

[zoki]

Hey Francesco, you have maybe forgot to push docker related files to your repo. I have sent you an email about my docker and nextjs issue.

[piotrprs]

Watching this clip I get strong urge to learn Italian language. 😀 Even English sound much better with this Italian accent. 😀

[undercontr]

if you have a dependent service in your docker compose like your nextjs app dependent to strapi or medusa in another service, nextjs app doesn't buid :/ i know how to opt out from SSG in pages router but app router is a bit complex.