Allow the user to run the Control API on a different port

[matiasinsaurralde]

Related to #354.

[buger]

Cool! Can you update PR description with steps on how to configure and test separate port?

[buger]

Do not forget that after merging we should update documentation.

[mvdan]

@matiasinsaurralde also please rebase onto master instead of merging master onto PR branches

[lonelycode]

Has this been tested with hot reload logic?

[buger]

Good point, linking #431

[matiasinsaurralde]

@lonelycode I was able to reproduce the issue (APIs not being loaded after reload), and after rewriting this part of listen it works fine.
@buger Will add the instructions now.

[matiasinsaurralde]

@mvdan Updated!

[lonelycode]

Lurvely

[matiasinsaurralde]

Test instructions

By default the control API will be exposed in the same IP/port the gateway is using. For example, to list the APIs:

curl -H 'x-tyk-authorization: 352d20ee67be67f6340b4c0605b044b7' http://localhost:8080/tyk/apis/

To configure a separate control API port you may set the control_api_port field in tyk.conf. If you set it to 7777, you may try this command:

curl -H 'x-tyk-authorization: 352d20ee67be67f6340b4c0605b044b7' http://localhost:7777/tyk/apis/

It shouldn't be available in the gateway port anymore!

[ilijabojanovic]

@buger This is feature request? If is please add label and milestone

[buger]

@ilijabojanovic this is PR, label and milestone added to underlying issue mentioned in description.

[ilijabojanovic]

@buger thanks for clarification

[buger]

@ilijabojanovic ready for testing as well

@matiasinsaurralde can you resolve conflicts in meantime.

[buger]

@matiasinsaurralde some of this conflicts potentially dangerous (in main.go), so pls fix conflicts before it goes to QA.

[buger]

@matiasinsaurralde bump

[matiasinsaurralde]

@leon Updated!

[buger]

@ConsM pls update documentation about control_api_port flag.

[ilijabojanovic]

@buger verified and approved for merge