ibm-cloud-docs / apiconnect

apiconnect
6 stars 25 forks source link

Publishing section truncated #6

Closed crandmck closed 7 years ago

crandmck commented 7 years ago

The section Publishing a LoopBack application to Bluemix from the CLI is cut off after the first two lines....

However, the source markdown has eight more steps: https://github.com/IBM-Bluemix-Docs/apiconnect/blob/master/creating_apis.md#publishing-a-loopback-application-to-bluemix-from-the-cli

I don't know why the rest of the content is not displayed, but it should be! As it is, the section is very confusing.

crandmck commented 7 years ago

@cadawson It doesn't look like the small change we discussed fixed this. Problem still occurs: https://console.stage1.bluemix.net/docs/services/apiconnect/creating_apis.html#pub_lb_app_cli

crandmck commented 7 years ago

@cadawson Any ideas?

cadawson commented 7 years ago

I've been working with it all morning trying to get it to work, with limited success. Still working with it. Doesn't make sense to me. Some similarly structured information is rendering fine.

cadawson commented 7 years ago

@crandmck ^^^

cadawson commented 7 years ago

This change has been pushed to master. Build should be done in 30 minutes or so. @crandmck

crandmck commented 7 years ago

It's fixed on staging: https://console.stage1.bluemix.net/docs/services/apiconnect/creating_apis.html#pub_lb_app_cli

But not (yet?) in production: https://console.bluemix.net/docs/services/apiconnect/creating_apis.html#publishing-a-loopback-application-to-bluemix-from-the-cli

cadawson commented 7 years ago

Yes, I see that. It does not look like prod is displaying the same version that is in git. Not sure if the build hasn't taken place yet, or is git is having issues processing an old file. I see the date on prod is 7/28, while the version in git is 8/1. I changed the date in git from 8/1 to 8/3 to hopefully force a build.

cadawson commented 7 years ago

I think this is fixed now. Take a look when you get a chance. Thanks!

crandmck commented 7 years ago

Yep, fixed! Thanks @cadawson