Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

757
Views
¿Cómo implementar la aplicación Nestjs en Digital Ocean?

Sigo recibiendo un error de implementación: comprobaciones de estado. Todo funciona bien en mi local con npm run start:dev . Tampoco muestra ningún error obvio en los registros. También estoy usando una gota de 5 dólares. También estoy usando el CICD integrado de Digital Ocean (PaaS).

implementar registros

 [2022-04-16 19:53:01] [2022-04-16 19:53:01] > yakkabot@0.0.1 start:prod /workspace [2022-04-16 19:53:01] > node dist/main [2022-04-16 19:53:01] [2022-04-16 19:53:02] [Nest] 17 - 04/16/2022, 7:53:02 PM LOG [NestFactory] Starting Nest application... [2022-04-16 19:53:02] [Nest] 17 - 04/16/2022, 7:53:02 PM LOG [InstanceLoader] HttpModule dependencies initialized +43ms [2022-04-16 19:53:02] [Nest] 17 - 04/16/2022, 7:53:02 PM LOG [InstanceLoader] ConfigHostModule dependencies initialized +0ms [2022-04-16 19:53:02] [Nest] 17 - 04/16/2022, 7:53:02 PM LOG [InstanceLoader] ConfigModule dependencies initialized +1ms [2022-04-16 19:53:02] [Nest] 17 - 04/16/2022, 7:53:02 PM LOG [InstanceLoader] YakkaBot dependencies initialized +0ms [2022-04-16 19:53:03] [Nest] 17 - 04/16/2022, 7:53:03 PM LOG [RoutesResolver] EthplorerController {/token-metrics}: +63ms [2022-04-16 19:53:03] [Nest] 17 - 04/16/2022, 7:53:03 PM LOG [RouterExplorer] Mapped {/token-metrics/topTokenHolders/:tokenId/:limit, GET} route +2ms [2022-04-16 19:53:03] [Nest] 17 - 04/16/2022, 7:53:03 PM LOG [NestApplication] Nest application successfully started +3ms []

construir registros

 [2022-04-16 19:51:24] Adding 2/2 app layer(s) [2022-04-16 19:51:24] Adding layer 'launcher' [2022-04-16 19:51:25] Adding layer 'config' [2022-04-16 19:51:25] Adding label 'io.buildpacks.lifecycle.metadata' [2022-04-16 19:51:25] Adding label 'io.buildpacks.build.metadata' [2022-04-16 19:51:25] Adding label 'io.buildpacks.project.metadata' [2022-04-16 19:52:06] *** Images (sha256:f46327d2fbb45599a64b071296ea4d9e477bf7b8202192643e79e98cbbe9aee1): [2022-04-16 19:52:06] <image-1> [2022-04-16 19:52:07] Reusing cache layer 'heroku/nodejs-engine:nodejs' [2022-04-16 19:52:07] Reusing cache layer 'heroku/nodejs-engine:toolbox' [2022-04-16 19:52:30] Reusing cache layer 'digitalocean/node:node_modules' [2022-04-16 19:52:32] => Uploaded the built image to the container registry [2022-04-16 19:52:32] => Build complete []

Configuración de implementación

over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

Creo que debería verificar nuevamente el puerto del servidor en el archivo principal, ¡tal vez no sea 3000! El puerto debe coincidir con el puerto en el servidor y el puerto en el océano digital

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!