ryan jarvinen

I would love to see support for manually providing a port value via `odo init --port PORTNUMBER`. If more than one port is detected, we may need the user to...

I ended up pushing a similar commit directly into the ocp-3.11 branch (https://github.com/openshift-labs/cloud-native-labs/commit/37ae96ef7d47e320a10199bcb567015e7dd47492). If that other change is headed toward `master` (through another merge or release process) then this PR...

Currently fixed in the `ocp-3.11` branch: https://github.com/openshift-labs/cloud-native-labs/commit/37ae96ef7d47e320a10199bcb567015e7dd47492 PR available against `master` if needed (feel free to delete if not): https://github.com/openshift-labs/cloud-native-labs/pull/13

+1 Thanks for calling this out in a separate issue

Thanks for the response. All of my nodejs demos run on port 8080. The nodejs devfile is set for port 3000. I'm not aware of any way to initialize my...

I like the idea of supporting `--port CONTAINERNAME:PORTNUMBER`

:+1:

Thanks @fitch - I tried the [stormboy/lifxjs](https://github.com/stormboy/lifxjs) repo, but I wasn't able to get it to discover, or to control my bulbs (which are running the 2.0 firmware).

**MY BAD** - my firewall was blocking port 56700 I'm able to detect the bulbs now. Thanks for testing @fitch

scan for tweets that include presentation urls. Generate a speaker page and leaderboard that takes advantage of github gist star counts to rank the talks