Managing Deployments

Once your app is deployed, you can manage it from the Apps > Deployed tab.

The Deployed Tab

The deployed tab shows all active deployments with:

• Status indicator — Color-coded dot showing current state
• Name and app ID
• Image tag — The container image version
• Replicas — Ready/total instance count
• Hostname — The public URL
• Created date

Status Indicators

Status	Description
Running	App is live and healthy
Deploying	Starting up (animated indicator)
Updating	Rolling update in progress (animated)
Pending	Waiting for resources (animated)
Stopped	Manually stopped
Failed	Error occurred
Deleting	Being removed (animated)

The page auto-refreshes every 5 seconds when deployments are in a transient state (deploying, updating, pending, deleting).

Deployment Detail

Click a deployment to open its detail page. From here you can:

Update the Image

Enter a new image tag and click Update to trigger a rolling update.

Edit Configuration

Modify these settings and click Save Changes:

• Port and replicas
• Resource preset (Starter, Standard, Performance, Heavy, Custom)
• Access control — Auth mode and minimum role
• Allowed/denied users — Restrict access to specific members
• Environment variables — Add, edit, or remove variables

View Container Logs

Toggle the logs panel to see real-time container output. Choose the number of tail lines (100, 200, 500, or 1000) and click refresh to get the latest logs.

TIP

Container logs show real-time output from the running container.

Deployment Lifecycle

Action	Effect
Start	Resumes a stopped deployment
Stop	Gracefully stops all replicas
Redeploy	Restarts with the current configuration
Delete	Permanently removes the deployment (requires confirmation)

Networking

• Public: one HTTPS endpoint per deployment (https://{slug}.{org}.nextepoch.cloud and any custom domains), routed to the configured container port. HTTP/1.1, WebSockets and gRPC-Web work; plain gRPC through the public endpoint does not.
• Inside the environment: sibling deployments reach each other by slug. HTTP services on http://{slug} (port 80) or the container port; anything else — Redis, Postgres, MQTT — on its natural port, e.g. redis://{slug}:6379. {slug}:80 also forwards to the container port (kept for compatibility with older setups).
• Not offered: public TCP/UDP endpoints, TLS passthrough, more than one port per deployment. Use a second deployment of the same app for a second listener. Public non-HTTP access is a platform request.

Troubleshooting

Symptom	What to check
Deployment stays Pending	Check resource requests, quotas, and whether the selected image can be pulled.
Deployment enters Failed	Open the deployment logs — the failure reason is almost always in the last lines.
App URL returns 401	Review access control and confirm the caller has the required role or token.
App URL returns 502/503	Confirm the container listens on the configured port and has at least one ready replica.
Update does not appear	Verify the image tag changed, then use Redeploy if the same tag was reused.

Next Steps

• Configure access control for your deployments
• Provision storage for your applications