--- ... routes: - route: example.com protocol: http2 - route: www.example.com/foo - route: tcp-example.com:1234 Manifest attributes If you use the routes attribute in conjunction with the host, hosts, domain, domains, or no-hostname attributes, an error results. Push flag options ...
I tried to reproduce this error locally by mimicking the process of building my app in Jenkins and deploying via Cloud Foundry'scfcli and I get the following error whenever I try to start the app withNODE_ENV=production node dist/index.js: Error: Cannot find module '<path>/next/routes-m...
Files master aws bin lib locales public routes screenshots views .dockerignore .gitignore .travis.yml Dockerfile LICENSE.md README.md app.js app.json azuredeploy.json config.js iisnode.yaml manifest.yml package-lock.json package.jsonBreadcrumbs nodeslackers / manifest.yml ...
--- ... routes: - route: example.com protocol: http2 - route: www.example.com/foo - route: tcp-example.com:1234 Manifest attributes If you use the routes attribute in conjunction with the host, hosts, domain, domains, or no-hostname attributes, an error results. Push flag options ...
Running the app in a production environment fails becauseroutes-manifest.jsoncannot be found Describe the bug I have a custom Node.js server written in Typescript and I'm trying to deploy to IBM Cloud. Whenever I deploy my.nextanddistdirectories, I end up getting the following error:Error:...