Another nice piece of work. but I have question After docker build you run the app and it was nestjs - hello world but in the last it was reactjs web app. how?
Help Required !! Thanks for the wornderful tutorial. But I am getting an erron in Cloud Run "The user-provided container failed to start and listen on the port defined provided by the PORT=3000 environment variable. Logs for this revision might contain more information."
Following this tutorial but stuck at docker run. Docker are running on exact port (8888), but when I accessed it, return ‘localhost didn’t send any data’. Any suggest?
I made the same thing, but in my case after create service cloud run, the end of process is giving the error below. The user-provided container failed to start and listen on the port defined provided by the PORT=80 environment variable. Logs for this revision might contain more information I am using the port 80 like the video Someone think the fix?
@@truelife9859 productive meetings are necessary when working on teams. Meaningless meatings are shit, but productive and goal-oriented meetings are a must-have for a well developed product. This comes from a dev that finds meetings boring, so yeah
Step 3/12 : COPY package*.json . When using COPY with more than one source file, the destination must be a directory and end with a / this works instead COPY package*.json ./
Very helpful - Thanks ! BTW, I got a permission error when using docker push. It seems that this error happens to Powershell users, the fix was in stackoverflow, the link is : stackoverflow.com/a/67595469/12991445
If you are wondering why it is showing a React app in the end, it is because I'm reusing video parts because the logic is the same.
Still accurate two years later, thanks mate !
You're a great teacher!
Thank you!
Another nice piece of work. but I have question
After docker build you run the app and it was nestjs - hello world
but in the last it was reactjs web app.
how?
You can build a React Js app and get it in static files, so in nest js you can serve this files without problems.
Thank so much! Do you have something with CloudSQL too?
Very helpful. Thanks !
Help Required !! Thanks for the wornderful tutorial. But I am getting an erron in Cloud Run "The user-provided container failed to start and listen on the port defined provided by the PORT=3000 environment variable. Logs for this revision might contain more information."
you should use PORT=80
You must provide the same port you are using to run your application on Cloud Run
Following this tutorial but stuck at docker run. Docker are running on exact port (8888), but when I accessed it, return ‘localhost didn’t send any data’. Any suggest?
Solved by -p 8888:3000 because nestjs default run on port 3000. New problem: still couldn’t deploy on Cloud Run :D
I made the same thing, but in my case after create service cloud run, the end of process is giving the error below.
The user-provided container failed to start and listen on the port defined provided by the PORT=80 environment variable. Logs for this revision might contain more information
I am using the port 80 like the video
Someone think the fix?
You must provide the same port you are using to run your application on Cloud Run
U know a lot of stuff , may I know ur age? Btw I am 18.
I'm 30, been coding since ~20
@@ScalableScripts damn bro why are you on youtube , why not doing a 6figures paying job?
I don't enjoy working for someone else, also corporate has a lot of meaningless meetings and tasks. I work harder on my own.
@@ScalableScripts that's super true nonsense meetings
@@truelife9859 productive meetings are necessary when working on teams. Meaningless meatings are shit, but productive and goal-oriented meetings are a must-have for a well developed product. This comes from a dev that finds meetings boring, so yeah
Step 3/12 : COPY package*.json .
When using COPY with more than one source file, the destination must be a directory and end with a /
this works instead
COPY package*.json ./
Very helpful - Thanks !
BTW, I got a permission error when using docker push.
It seems that this error happens to Powershell users, the fix was in stackoverflow, the link is :
stackoverflow.com/a/67595469/12991445
Thanks, I had the same error