Develop Serverless Apps with Firebase: Challenge Lab recensioni

Tanvi P. · Recensione inserita oltre 2 anni fa

Rutuja C. · Recensione inserita oltre 2 anni fa

Rutuja C. · Recensione inserita oltre 2 anni fa

Abdul M. · Recensione inserita oltre 2 anni fa

Christian K. · Recensione inserita oltre 2 anni fa

Sometimes providing us-central1 is not accessible in the list. Too easy for a challenge lab.

Kyrylo B. · Recensione inserita oltre 2 anni fa

us-central1 is not accessible in the list.

Kyrylo B. · Recensione inserita oltre 2 anni fa

Filip K. · Recensione inserita oltre 2 anni fa

Filip K. · Recensione inserita oltre 2 anni fa

Derick Alejandro B. · Recensione inserita oltre 2 anni fa

jeremy b. · Recensione inserita oltre 2 anni fa

Aldo Daniel C. · Recensione inserita oltre 2 anni fa

Fabrizio F. · Recensione inserita oltre 2 anni fa

David L. · Recensione inserita oltre 2 anni fa

The examples required to use deprecated container registry and failed when using working artifact registry. Cloud build was not checked.

Maciej K. · Recensione inserita oltre 2 anni fa

Very

Amit K. · Recensione inserita oltre 2 anni fa

Yasumoto T. · Recensione inserita oltre 2 anni fa

Rafał Ł. · Recensione inserita oltre 2 anni fa

Kishore M. · Recensione inserita oltre 2 anni fa

Igor K. · Recensione inserita oltre 2 anni fa

Martin C. · Recensione inserita oltre 2 anni fa

Wynston L. · Recensione inserita oltre 2 anni fa

VARUN S. · Recensione inserita oltre 2 anni fa

the data import script fails note: 'Exception occurred in retry method that was not classified as transient'

Guillaume L. · Recensione inserita oltre 2 anni fa

Okay, this lab would be awesome and great IF the instructions were clear! Not saying they're not straightforward, what made me angry and had to end the lab before completing it, is that it has no clear instructions on what to build with what parameters, what toolage(i.e. CLI or console) to be used for the steps. For instance, the when creating the Firestore database, the instructions said to create one. But it did not mention to leave it as default. Some people like to name their databases not default. So this made me go down on a node module troubleshooting, when the only change that made it work was to create a default database... Frustrating! Similarly, the image build to GCR... the image has to be named properly in order for the Cloud Run service to be able to be checked by the systems. Once again, the instructions were not clear enough! Why can't we have some clear poitns/instructions on what to do and what is there to be achieved? I highly suggest this lab to be reworked. Not saying it is not useful, all I'm saying is that in the limited timewindow allowed, this simply cannot be troubleshot while the timer is ticking, and hoping that the end goal will be achieved.

Danny M. · Recensione inserita oltre 2 anni fa