如何让我的 Next.js 应用程序在 Azure 应用程序服务 运行 ubuntu-latest 中启动?
How do I get my Next.js app to start in an Azure App Service running ubuntu-latest?
我正在尝试在 Azure 上部署我的 Next.js (SSR)。
我有一个发布整个根文件夹的构建管道(不仅仅是静态应用程序的 .next 文件夹)
trigger:
- main
pool:
vmImage: "ubuntu-latest"
# Set variables
variables:
directory: .
steps:
- task: NodeTool@0
inputs:
versionSpec: "16.x"
displayName: "Install Node.js"
- script: yarn
displayName: "Install dependencies"
workingDirectory: $(directory)
- task: Cache@2
displayName: 'Cache .next/cache'
inputs:
key: next | $(Agent.OS) | yarn.lock
path: '$(System.DefaultWorkingDirectory)/.next/cache'
- script: yarn build
displayName: "Build for production"
workingDirectory: $(directory)
- task: CopyFiles@2
displayName: "Copy files"
inputs:
sourceFolder: "$(directory)"
Contents: "**/*"
TargetFolder: "$(Build.ArtifactStagingDirectory)"
cleanTargetFolder: true
- task: ArchiveFiles@2
displayName: "Archive files"
inputs:
rootFolderOrFile: "$(Build.ArtifactStagingDirectory)"
includeRootFolder: false
archiveType: zip
archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
replaceExistingArchive: true
- task: PublishBuildArtifacts@1
displayName: "Publish build artifacts"
inputs:
pathtoPublish: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
我在项目根文件夹中还有一个文件 ecosystem.config.js
,其中包含内容(如 this answer 中所述)
module.exports = {
apps: [
{
name: "app-name",
script: "./node_modules/.bin/next",
args: "start -p " + (process.env.PORT || 3000),
watch: false,
autorestart: true,
},
],
};
如前所述,构建管道将整个根文件夹发布为发布管道的 .zip
工件。
我有一个发布管道,可以将项目部署到应用服务并运行启动命令(来自 same answer as before and Microsoft docs)
pm2 start /home/site/wwwroot/ecosystem.config.js --no-daemon
package.json
脚本部分
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
}
我可以看到构建和发布管道都已成功完成,我可以看到根项目文件夹中的文件位于 /home/site/wwwroot
,但是当我访问该站点时,我得到的是
通往诊断资源的 link 并没有提供太多的洞察力,但如果我检查应用服务中 docker 容器的日志,我会看到
2022-05-16T11:03:07.083870878Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.085484100Z 11:03:07 PM2 | App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.086237210Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] starting in -fork mode-
2022-05-16T11:03:07.087102722Z 11:03:07 PM2 | App [app-name:0] starting in -fork mode-
2022-05-16T11:03:07.103212737Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] online
2022-05-16T11:03:07.105379766Z 11:03:07 PM2 | App [app-name:0] online
2022-05-16T11:03:07.370010000Z 11:03:07 0|app-name | Error: Cannot find module '../build/output/log'
2022-05-16T11:03:07.372651936Z 11:03:07 0|app-name | Require stack:
2022-05-16T11:03:07.372950840Z 11:03:07 0|app-name | - /home/site/wwwroot/node_modules/.bin/next
2022-05-16T11:03:07.373244644Z 11:03:07 0|app-name | at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
2022-05-16T11:03:07.373521147Z 11:03:07 0|app-name | at Module.Hook._require.Module.require (/usr/local/lib/node_modules/pm2/node_modules/require-in-the-middle/index.js:61:29)
2022-05-16T11:03:07.373779851Z 11:03:07 0|app-name | at require (node:internal/modules/cjs/helpers:94:18)
2022-05-16T11:03:07.374053954Z 11:03:07 0|app-name | at Object.<anonymous> (/home/site/wwwroot/node_modules/.bin/next:7:35)
2022-05-16T11:03:07.375460973Z 11:03:07 0|app-name | at Module._compile (node:internal/modules/cjs/loader:1101:14)
2022-05-16T11:03:07.375473673Z 11:03:07 0|app-name | at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
2022-05-16T11:03:07.375477573Z 11:03:07 0|app-name | at Module.load (node:internal/modules/cjs/loader:981:32)
2022-05-16T11:03:07.375480873Z 11:03:07 0|app-name | at Function.Module._load (node:internal/modules/cjs/loader:822:12)
2022-05-16T11:03:07.375485473Z 11:03:07 0|app-name | at Object.<anonymous> (/usr/local/lib/node_modules/pm2/lib/ProcessContainerFork.js:33:23)
2022-05-16T11:03:07.375693476Z 11:03:07 0|app-name | at Module._compile (node:internal/modules/cjs/loader:1101:14) {
2022-05-16T11:03:07.376825291Z 11:03:07 0|app-name | code: 'MODULE_NOT_FOUND',
2022-05-16T11:03:07.377099895Z 11:03:07 0|app-name | requireStack: [ '/home/site/wwwroot/node_modules/.bin/next' ]
2022-05-16T11:03:07.377376699Z 11:03:07 0|app-name | }
2022-05-16T11:03:07.378681516Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.379377325Z 2022-05-16T11:03:07: PM2 log: Script /home/site/wwwroot/node_modules/.bin/next had too many unstable restarts (16). Stopped. "errored"
2022-05-16T11:03:07.384267191Z 11:03:07 PM2 | App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.384723497Z 11:03:07 PM2 | Script /home/site/wwwroot/node_modules/.bin/next had too many unstable restarts (16). Stopped. "errored"
有人知道如何从这里开始吗?
提前致谢!
使用 Kudu 检查您的 wwwroot 目录(开发工具 -> 高级工具)。默认情况下,Azure Devops 发布管道未复制 files/folders 从“.”开始,因此文件夹“/node_modules/.bin/”可能尚未复制到 Azure App Service
我通过将 ecosystem.config.js
中的 start-up 脚本更改为
解决了这个问题
./node_modules/next/dist/bin/next
而不是
./node_modules/.bin/next
我的新ecosystem.config.js
module.exports = {
apps: [
{
name: "app-name",
script: "./node_modules/next/dist/bin/next",
args: "start -p " + (process.env.PORT || 3000),
watch: false,
autorestart: true,
},
],
};
我正在尝试在 Azure 上部署我的 Next.js (SSR)。
我有一个发布整个根文件夹的构建管道(不仅仅是静态应用程序的 .next 文件夹)
trigger:
- main
pool:
vmImage: "ubuntu-latest"
# Set variables
variables:
directory: .
steps:
- task: NodeTool@0
inputs:
versionSpec: "16.x"
displayName: "Install Node.js"
- script: yarn
displayName: "Install dependencies"
workingDirectory: $(directory)
- task: Cache@2
displayName: 'Cache .next/cache'
inputs:
key: next | $(Agent.OS) | yarn.lock
path: '$(System.DefaultWorkingDirectory)/.next/cache'
- script: yarn build
displayName: "Build for production"
workingDirectory: $(directory)
- task: CopyFiles@2
displayName: "Copy files"
inputs:
sourceFolder: "$(directory)"
Contents: "**/*"
TargetFolder: "$(Build.ArtifactStagingDirectory)"
cleanTargetFolder: true
- task: ArchiveFiles@2
displayName: "Archive files"
inputs:
rootFolderOrFile: "$(Build.ArtifactStagingDirectory)"
includeRootFolder: false
archiveType: zip
archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
replaceExistingArchive: true
- task: PublishBuildArtifacts@1
displayName: "Publish build artifacts"
inputs:
pathtoPublish: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
我在项目根文件夹中还有一个文件 ecosystem.config.js
,其中包含内容(如 this answer 中所述)
module.exports = {
apps: [
{
name: "app-name",
script: "./node_modules/.bin/next",
args: "start -p " + (process.env.PORT || 3000),
watch: false,
autorestart: true,
},
],
};
如前所述,构建管道将整个根文件夹发布为发布管道的 .zip
工件。
我有一个发布管道,可以将项目部署到应用服务并运行启动命令(来自 same answer as before and Microsoft docs)
pm2 start /home/site/wwwroot/ecosystem.config.js --no-daemon
package.json
脚本部分
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
}
我可以看到构建和发布管道都已成功完成,我可以看到根项目文件夹中的文件位于 /home/site/wwwroot
,但是当我访问该站点时,我得到的是
通往诊断资源的 link 并没有提供太多的洞察力,但如果我检查应用服务中 docker 容器的日志,我会看到
2022-05-16T11:03:07.083870878Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.085484100Z 11:03:07 PM2 | App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.086237210Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] starting in -fork mode-
2022-05-16T11:03:07.087102722Z 11:03:07 PM2 | App [app-name:0] starting in -fork mode-
2022-05-16T11:03:07.103212737Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] online
2022-05-16T11:03:07.105379766Z 11:03:07 PM2 | App [app-name:0] online
2022-05-16T11:03:07.370010000Z 11:03:07 0|app-name | Error: Cannot find module '../build/output/log'
2022-05-16T11:03:07.372651936Z 11:03:07 0|app-name | Require stack:
2022-05-16T11:03:07.372950840Z 11:03:07 0|app-name | - /home/site/wwwroot/node_modules/.bin/next
2022-05-16T11:03:07.373244644Z 11:03:07 0|app-name | at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
2022-05-16T11:03:07.373521147Z 11:03:07 0|app-name | at Module.Hook._require.Module.require (/usr/local/lib/node_modules/pm2/node_modules/require-in-the-middle/index.js:61:29)
2022-05-16T11:03:07.373779851Z 11:03:07 0|app-name | at require (node:internal/modules/cjs/helpers:94:18)
2022-05-16T11:03:07.374053954Z 11:03:07 0|app-name | at Object.<anonymous> (/home/site/wwwroot/node_modules/.bin/next:7:35)
2022-05-16T11:03:07.375460973Z 11:03:07 0|app-name | at Module._compile (node:internal/modules/cjs/loader:1101:14)
2022-05-16T11:03:07.375473673Z 11:03:07 0|app-name | at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
2022-05-16T11:03:07.375477573Z 11:03:07 0|app-name | at Module.load (node:internal/modules/cjs/loader:981:32)
2022-05-16T11:03:07.375480873Z 11:03:07 0|app-name | at Function.Module._load (node:internal/modules/cjs/loader:822:12)
2022-05-16T11:03:07.375485473Z 11:03:07 0|app-name | at Object.<anonymous> (/usr/local/lib/node_modules/pm2/lib/ProcessContainerFork.js:33:23)
2022-05-16T11:03:07.375693476Z 11:03:07 0|app-name | at Module._compile (node:internal/modules/cjs/loader:1101:14) {
2022-05-16T11:03:07.376825291Z 11:03:07 0|app-name | code: 'MODULE_NOT_FOUND',
2022-05-16T11:03:07.377099895Z 11:03:07 0|app-name | requireStack: [ '/home/site/wwwroot/node_modules/.bin/next' ]
2022-05-16T11:03:07.377376699Z 11:03:07 0|app-name | }
2022-05-16T11:03:07.378681516Z 2022-05-16T11:03:07: PM2 log: App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.379377325Z 2022-05-16T11:03:07: PM2 log: Script /home/site/wwwroot/node_modules/.bin/next had too many unstable restarts (16). Stopped. "errored"
2022-05-16T11:03:07.384267191Z 11:03:07 PM2 | App [app-name:0] exited with code [1] via signal [SIGINT]
2022-05-16T11:03:07.384723497Z 11:03:07 PM2 | Script /home/site/wwwroot/node_modules/.bin/next had too many unstable restarts (16). Stopped. "errored"
有人知道如何从这里开始吗?
提前致谢!
使用 Kudu 检查您的 wwwroot 目录(开发工具 -> 高级工具)。默认情况下,Azure Devops 发布管道未复制 files/folders 从“.”开始,因此文件夹“/node_modules/.bin/”可能尚未复制到 Azure App Service
我通过将 ecosystem.config.js
中的 start-up 脚本更改为
./node_modules/next/dist/bin/next
而不是
./node_modules/.bin/next
我的新ecosystem.config.js
module.exports = {
apps: [
{
name: "app-name",
script: "./node_modules/next/dist/bin/next",
args: "start -p " + (process.env.PORT || 3000),
watch: false,
autorestart: true,
},
],
};