I have deployed a docker image on PCF. But not able to register API.
Is there any UI available for Tyk on PCF?
By PCF I’m assuming you mean Pivotal Cloud Foundry?
Did you try following any of the docker guides on our site? We don’t have specific guides for any cloud provider, but the compose script is pretty consice in how things are laid out.
While installing Tyk on Red Hat…
Running this command giving error 404:
wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-5.noarch.rpm
Errror log:
Resolving dl.fedoraproject.org (dl.fedoraproject.org)… 209.132.181.27, 209.132.181.23, 209.132.181.24, …
Connecting to dl.fedoraproject.org (dl.fedoraproject.org)|209.132.181.27|:80… connected.
HTTP request sent, awaiting response… 404 Not Found
2016-07-12 11:37:23 ERROR 404: Not Found.
Looks like they updated the release version, try:
http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-7.noarch.rpm
Yes that worked thanks 
But the further commands are also giving errors.
like-
Command: sudo rpm -ivh epel-release-7-5.noarch.rpm
error: open of epel-release-7-5.noarch.rpm failed: No such file or directory
Command : sudo yum -q makecache -y --disablerepo='*' --enablerepo='tyk_tyk-gateway' --enablerepo=epel info zabbix
error : File contains no section headers.
file: file:///etc/yum.repos.d/tyk_tyk-gateway.repo, line: 1
‘\x1b[A\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\x1b[C\n’
For command : sudo rpm -ivh epel-release-7-5.noarch.rpm
I Used : sudo rpm -ivh epel-release-7-7.noarch.rpm
But it gave me warning and conflicts-
warning: epel-release-7-7.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
Preparing… ################################# [100%]
file /etc/yum.repos.d/epel-testing.repo from install of epel-release-7-7.noarch conflicts with file from package epel-release-6-8.9.amzn1.noarch
file /etc/yum.repos.d/epel.repo from install of epel-release-7-7.noarch conflicts with file from package epel-release-6-8.9.amzn1.noarch
will it be a problem?
Hmmm, it shouldn’t be. Those lines are designed to basically get redis installed onRedHat, which requires EPEL
Since RH insists on secure repos they check crypto signatures. If you are setting up a dev environment, this should be ok. Obviously for a production env it might be easier to just compile redis for your platform, or install it from a supported repo 