Desenvolvimento de apps – Como implantar uma API para o aplicativo de teste: Node.js avaliações

Javier M. · Revisado há about 5 years

Wiktor K. · Revisado há about 5 years

Marijana M. · Revisado há about 5 years

聡杉. · Revisado há about 5 years

Marijana M. · Revisado há about 5 years

Marcos A. · Revisado há about 5 years

Vivek K. · Revisado há about 5 years

Javier M. · Revisado há about 5 years

Ramya C. · Revisado há about 5 years

Oz S. · Revisado há about 5 years

this one was rough. somehow, I saw the CONFIG_ID and SERVICE_NAME as the things I should set as key in metadata. It works, but the metrics never did show up in the monitoring page but I can't be arsed to dig into why after the other stuff.

Baron C. · Revisado há about 5 years

Peter S. · Revisado há about 5 years

Austin S. · Revisado há about 5 years

Derrick C. · Revisado há about 5 years

Martez B. · Revisado há about 5 years

I would like more detail on what actually happens to the quiz-api directory after it is copied to the compute instance. Details on how exactly it is being used - I found the lab glossed over this by requesting I just run some scripts.

Niall M. · Revisado há about 5 years

Had an issue viewing the api JSON payload: http://quiz-api.endpoints.qwiklabs-gcp-02-a765130466ec.cloud.goog/api/quizzes/places returned { "code": 13, "message": "BAD_GATEWAY", "details": [ { "@type": "type.googleapis.com/google.rpc.DebugInfo", "stackEntries": [], "detail": "application" } ] } In nginx log I would see this error (the console is not available so I cant paste the exact error...): ... connect() failed (111: Connection refused) while connecting to upstream 127.0.0.1:8081/...//api/quizzes/places

Francois L. · Revisado há about 5 years

Arnaud R. · Revisado há about 5 years