我只是想尝试一下 Saleor，我只是使用 Heroku 按钮的一键式选项来一次部署所有三个。
不过除了storefont。另外两个非常成功，现在我可以通过我的仪表板应用程序访问我的销售或核心。说到店面部署失败，我在 Web 控制台上看到 heroku 的构建日志时注意到一些 db 错误。
我怀疑它可能与一些虚拟数据有关。当我在 Saleor 网站上阅读有关 saleor 部署的文档时，他们说“populatedb”不应该在没有明确“为什么”的情况下对生产模式进行。
而且我认为这两者（我的店面部署失败和对 db 虚拟数据的评论）彼此有关？我手动删除了仪表板页面上的虚拟数据库数据，但仍然通过 heroku 进行店面部署失败。
我应该怎么办？
这是我的最后几行日志：
Detected both "build" and "heroku-postbuild" scripts
Running heroku-postbuild
> saleor-site@3.0.0-a.0 heroku-postbuild /tmp/build_4b72e375
> npm run build
> saleor-site@3.0.0-a.0 build /tmp/build_4b72e375
> next build
warn - React 17.0.1 or newer will be required to leverage all of the upcoming features in Next.js 11. Read more: https://nextjs.org/docs/messages/react-version
info - Loaded env from /tmp/build_4b72e375/.env.production
info - Loaded env from /tmp/build_4b72e375/.env
info - Using webpack 4. Reason: future.webpack5 option disabled https://nextjs.org/docs/messages/webpack5
warn - No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
info - Checking validity of types...
info - Creating an optimized production build...
Warning: Built-in CSS support is being disabled due to custom CSS configuration being detected.
See here for more info: https://nextjs.org/docs/messages/built-in-css-disabled
info - Using external babel configuration from /tmp/build_4b72e375/babel.config.js
warn - Compiled with warnings
chunk c2a338df9f7a158c73f6eb10485bfa280f05fa08_CSS [mini-css-extract-plugin]
Conflicting order between:
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/Carousel/scss/index.scss
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/NotFound/scss/index.scss
chunk c2a338df9f7a158c73f6eb10485bfa280f05fa08_CSS [mini-css-extract-plugin]
Conflicting order between:
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/globalStyles/scss/variables.scss
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/NotFound/scss/index.scss
chunk c2a338df9f7a158c73f6eb10485bfa280f05fa08_CSS [mini-css-extract-plugin]
Conflicting order between:
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/Loader/scss/index.scss
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/NotFound/scss/index.scss
chunk c2a338df9f7a158c73f6eb10485bfa280f05fa08_CSS [mini-css-extract-plugin]
Conflicting order between:
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/LoginForm/scss/index.scss
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/NotFound/scss/index.scss
chunk c2a338df9f7a158c73f6eb10485bfa280f05fa08_CSS [mini-css-extract-plugin]
Conflicting order between:
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/MenuDropdown/scss/index.scss
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/NotFound/scss/index.scss
chunk c2a338df9f7a158c73f6eb10485bfa280f05fa08_CSS [mini-css-extract-plugin]
Conflicting order between:
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/Message/scss/index.scss
* css ./node_modules/css-loader??ref--5-1!./node_modules/sass-loader/lib/loader.js!./src/components/NotFound/scss/index.scss
static/chunks/4b9541f122ed8b2d7ca4f3d6c2ccfa88f43c03cf.6b18c609dd544e1c1230.js is 4.93 MB, and won't be precached. Configure maximumFileSizeToCacheInBytes to change this limit.
info - Collecting page data...
Warning: fragment with name Price already exists.
graphql-tag enforces all fragment names across your application to be unique; read more about
this in the docs: http://dev.apollodata.com/core/fragments.html#unique-names
Warning: fragment with name ProductPricingField already exists.
graphql-tag enforces all fragment names across your application to be unique; read more about
this in the docs: http://dev.apollodata.com/core/fragments.html#unique-names
(node:7916) UnhandledPromiseRejectionWarning: Error: Network error: request to http://localhost:8000/graphql/ failed, reason: connect ECONNREFUSED 127.0.0.1:8000
at new ApolloError (/tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:92:26)
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:1588:34
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:2008:15
at Set.forEach (<anonymous>)
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:2006:26
at Map.forEach (<anonymous>)
at QueryManager.broadcastQueries (/tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:2004:20)
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:1483:29
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:7916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:7916) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:7916) UnhandledPromiseRejectionWarning: Error: Network error: request to http://localhost:8000/graphql/ failed, reason: connect ECONNREFUSED 127.0.0.1:8000
at new ApolloError (/tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:92:26)
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:1588:34
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:2008:15
at Set.forEach (<anonymous>)
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:2006:26
at Map.forEach (<anonymous>)
at QueryManager.broadcastQueries (/tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:2004:20)
at /tmp/build_4b72e375/node_modules/apollo-client/bundle.umd.js:1483:29
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:7916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
-----> Timed out running buildpack Node.js
Terminated