Skip to main content
An Internal service is a lot like Web service, but it is not exposed to public internet. It is available to get used from within the environment by other services.

​
Port

When you create a service, you must provide port number where your Dockerfile exposes the running code.

​
Reach it from your machine

Because an internal service has no public URL, you cannot open it in a browser or point a local tool at it. Forward its port to your machine instead:
That binds the same port locally that the service listens on, so http://localhost:<port> reaches it for as long as the command runs. See CLI usage for the full set of options.

​
Number of replicas

For redundancy, ensure you set at least 2 as the number of replicas. This is a best practice yet you can enter 1 if it better suits your use case.

​
No downtime deployments

All deployments are no-downtime deployments. When LocalOps deploys your code, it brings up new containers with new code first. If they become healthy, old containers will be stopped.

​
Logs

You can see logs of running containers via the in-built Grafana dashboard. Navigate to Monitor tab to login to Grafana dashboard. Within Grafana dashboard, filter to see app-services namespace logs. To watch one service as it runs, ops logs --env staging --svc <service-name> streams the same output to your terminal. See CLI usage. You can create any number of internal services to suit your application architecture. All of the above will be applicable for each of them.