Invalid PORT value

Open
#13 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, coffeescript, node.js
Domain
backend, cloud

Research direction

No file or test is named. Start by locating getAppEnv and the vcap environment parsing, then reproduce the Azure case where PORT is a named pipe rather than a number. Done means the Azure value is handled without breaking Cloud Foundry environment handling, with coverage for both forms.

Written by the indexing model from the issue text.

Description

Trying to keep a codebase compatible between CloudFoundry (Bluemix) and Azure.

I'm getting an error on getAppEnv, because under Azure, port is not a number but a named pipe (/\\.\pipe\xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

I was hoping to use cfenv with the vcap option filled some other way when running "locally" on Azure.

Dominant language
CoffeeScript
Stars
74
Forks
25
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry-community/node-cfenv

All issues in cloudfoundry-community/node-cfenv

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.