Notice about the port to access Kibana.

[jgbarah]

This is just a simple change to CONTRIBUTING.md, addressing #7296 (only a mitigation measure).

[elasticsearch-release]

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then say 'jenkins, test it'.

[jgbarah]

I just signed the CLA, BTW, even when checks says otherwise.

[panda01]

jenkins, test it

[ppisljar]

LGTM

[elasticmachine]

Can one of the admins verify this patch?

[jgbarah]

Anything about this? If you don't find it appropriate, I can just close it...

[thomasneirynck]

jenkins, test this

[thomasneirynck]

hi @jgbarah,

thanks for adding the information!

1. For the CI to succeed, this will needs to be rebased on the latest master, the contributing page has evolved quite a bit since you originally submitted this.

I'd splice it in here: https://github.com/elastic/kibana/blame/master/CONTRIBUTING.md#L115

2. I would also edit some typos. Since npm start launches in dev mode, I also trimmed some redundant information.

Now you can point your web browser to https://localhost:5601 and start using Kibana! When running npm start, Kibana launches in dev-mode also listens on port 5603, and you will see a notice in the server log about this. But the public access is on port 5601.

[epixa]

I'm going to close this out due to inactivity. Please feel free to resubmit if you pick this back up again!