dhmlau
commented
5 years ago @cloudwheels, please ignore my previous comment. I think the better way to get this working is to add this line in src/index.ts:
options.rest.host = appEnv.isLocal ? options.rest.host : appEnv.host;i.e.
export async function main(options: ApplicationConfig = {}) {
// Set the port assined for the app
if (!options) options = {};
if (!options.rest) options.rest = {};
options.rest.port = appEnv.isLocal ? options.rest.port : appEnv.port;
// ------- ADD THIS LINE ----------
options.rest.host = appEnv.isLocal ? options.rest.host : appEnv.host;
// ---------------------------------
const app = new TodoListApplication(options);I'll submit a PR to update the docs. Thanks for reporting this issue.
~@cloudwheels, I'm just trying out as well. It might be related to the recent change: https://github.com/strongloop/loopback-next/commit/2e7d4bb6e7b30aedfcc373a0d2bed3c0f1ad07c8. My workaround is not to use the config value in index.js, i.e.~
cloudwheels
Description / Steps to reproduce / Feature proposal
cf(as per deployment docks),ibmcloud cfbx(as per the cloud foundry node.js documentation after setting up an app. There are very few examples of this process around and those that exist seem to be conflicting, although they all seem to achieve the same results. Depending on which you choose and what prompts you receive, it can take some time to work out exactly what the required 'endpoint', 'org' and 'space' parameters for logging in and settings app endpoints. This is not covered at all in the deployment documentation.bxand specifying app name seemed to negate the need for this.Current Behavior
The app seems to build, start successfully and then crash, most lately / consistently with exit code 137 (which may possibly indicate memory problems with the cf container?). The app's routes are not available in the cloud. Extract of log, my package.json & node version below.
Please help - this has been driving me mental for 24hours, I've had plenty of stabs at different approaches but it just doesn't seem to work. I must be missing something really obvious but I have the fear that this version is all a bit bleeding edge right now and things seems to be in a state of flux with the IBM CLI tools!