Getting startedFerry and Render
Network, settings and tools
Ferry has the private network, the domains, the limits and the logs of Render.
Your custom domain goes to the proxy. The proxy answers with HTTPS.
1 / 3
| Render feature | In Ferry |
|---|---|
| Environment variables, environment groups | Yes. Ferry does not have secret files. |
Private network (service-name:port) | Yes: a Docker bridge network with DNS aliases |
| Custom domains, free TLS | Yes: Let’s Encrypt (ACME HTTP-01 challenge) |
| Manual scaling | Yes: the instances are behind round-robin load balancing in the proxy |
Instance types (plan) | Yes: memory and CPU limits for each service and datastore. The server defaults are 512 MiB and 1 CPU for each container. Ferry changes the plan of a blueprint into limits. |
| Logs (build and runtime, live tail), basic metrics | Yes: Server-Sent Events streams. CPU and memory of each instance, next to its limits. Ferry flags each OOM kill. |
| Dashboard, CLI, REST API | Yes |
See the use of each instance
Terminal
$ ferry status node-hellonode-hello: live — 1/1 instance(s) runningINSTANCE DEPLOY STATE PORT CPU MEMORY RESTARTS STARTED82e2be 4415b359 running 62694 4.7% / 1 CPU 24.2 MiB / 512.0 MiB 0 8s ago