opencloudportDocs

Your app's address

Where an app answers on the internet, how that address is made, and how to give it your own.

Every app gets its own address the moment it has compute. Until you deploy code it shows a starter page; after that, it runs your code.

The address you get

Each app has a fixed resource name, made when the app is created, like ocp-aabd5c1cfc91d7b629a0. Its address is that name on opencloudport's apps domain:

https://<resource name>.<apps domain>
  • The address never changes, even if you rename the app.
  • You'll find it on the app's page in the dashboard, under its name.
  • A paused app still answers at its address, with a short "This app is paused." page and status 503, so visitors aren't shown errors.

App objects from the API include it as url, and every address the app answers at as addresses (its own address first, then its platform address and custom domains, each with status):

{
  "id": "app_…",
  "url": "https://ocp-aabd5c1cfc91d7b629a0.<apps domain>",
  "addresses": [
    { "url": "https://ocp-aabd5c1cfc91d7b629a0.<apps domain>", "kind": "default", "status": "active" },
    { "url": "https://shop.example.com", "kind": "custom", "status": "pending" }
  ]
}

Your own domain

You can serve an app at a domain you own, like shop.example.com, or, if you run many apps for your own customers, at <name>.<your platform domain>. Both get a certificate automatically once the domain points at opencloudport. See Domains.

When you're developing locally

Running opencloudport's dev server yourself, apps answer at http://<resource name>.localhost:3000. Most browsers send every *.localhost name to your own computer, so no setup is needed.

On this page