Confused about installation

[kyb3r]

I have cloned the repo and then did the docker-compose up -d command, It seems like it works since when I access the server from my browser it shows the "ceryx no app here" page. However I can't seem to access the ceryx-api at all.

There are no ports exposed for it. I have tried making requests to http://localhost:5555 but they never connect to anything.

Am I doing something wrong, I'm not that familiar with docker, and I'm trying to write a script that will dynamically add routes that I will run on the VPS.

[parisk]

Hello @kyb3r,

The Ceryx API is intentionally not exposed. Currently it has not any authentication mechanism, which makes it completely unsuitable for public exposure.

To access the Ceryx API run the following command:

cd /path/to/ceryx/

docker-compose exec api bash
curl localhost:5555 -X POST -d '{"source": "...", "target": "...", "settings": {...}}'

---

This should definitely be clarified in the README, so I am adding the documentation label.

[kyb3r]

Thanks @parisk! I have another question, how can I refer to localhost as a target? I currently have a bunch of apps that are running that don't use docker, but I don't know how to refer to them. Currently, I am assuming localhost refers to the docker container itself.

[parisk]

There are two ways to do this:

1. Expose ceryx to the host network. If you do this though, you won't be able to use other Docker networks though.
2. Expose these applications in a network interface other than localhost. Ceryx should be able to reach them by using ip:port.

[rnixx]

Hi, i'm planning a setup where i want the dynamic reverse proxy accessible via public IP, and the API exposed on an internal IP. How can i achieve this?

[parisk]

Hi @rnixx! Deploying Ceryx in either:

• Docker: https://github.com/sourcelair/ceryx#running-ceryx, or
• Kubernetes: https://github.com/sourcelair/ceryx#running-ceryx-in-kubernetes

should do the work for you by exposing the API only in the internal network named api.