Thanks for the info!

Glad it was helpful!

Glad it helped!

Yeah I wonder. I didn't need to use it in the case of this build, but to be fair, it's an 'out the box' NextJS app. Perhaps once you have a bunch of routes/pages/etc the permissions become a problem. Or there's some other reason .. Could you link one of these tutorials perhaps? I'd like to see if there is some context I'm missing.

Have you figured out how to deploy with secrets? I am looking for that as well

Nice! Was hoping someone would want that. I'll create video dedicated to that topic specifically .. watch this space 😉

@@techedemic Some people say that alpine is not recommended for production and instead we should make multistage building but multistage is not as simple as we think.

Have a look at kzfaq.info/get/bejne/e7OUabeUtt7Lp2Q.html

Glad you liked it! I'm working on something new.... out soon 😉

It's because it's receveing something that cannot parse into a json. If you don't care about the view of the response you can use res.status(200) without .json(....)

Express is a framework for handling http(s) based requests. In it's simplest form, it handles the typical HTTP GET, POST, PUT, DELETE methods for you, but it supports middleware which means there is an vast array of utilities you can include as part of your express setup. Things like PassportJS (for authentication) is an example of a middleware library you can include with ExpressJS. Yes, node does have http/s functionality baked in, but Express is more comprehensive functionality wise and simplifies things tremendously. Other frameworks similar to express include Koa. I hope this answers your question?

Yeah the false pretence that everything "just works" is what sometimes puts people off because they don't get it right as easily as some videos make it look. Glad you liked it :)

Thanks man! Comments like these means a lot and inspires me to make more...

Theme is marketplace.visualstudio.com/items?itemName=wesbos.theme-cobalt2 Plugins... ooph..I use a lot, but the ones I cannot live without include:"ESLint", "Live Share", "Prettier"

@@techedemic perfect thanks

Remember, the idea is not to use the '.env-local' method in production. In production, these values should be passed via the command line as ENVIRONMENT VARIABLES. As such, the values should come from the environment. There are many ways to achieve this. For the sake of this video and for local development, storing these values in clear text should not be an issue. Also, don't push the `.env-local` file to git. I did it in this case to give you full access to the source coude after the fact but it's not good practice to do so in 'real life' You just gave my an idea for a topic for my next video :).. "Environment Variables in Node"

Glad I could help you. What topic would you be interested in? Anything specific?

It's a pleasure! I'll be making many more along the same lines... so remember to hit that 'subscribe' button and you'll be notified when they are uploaded!