Cloud Apps
Deploying your first app
Pick from the catalogue, choose a subscription and a size, and the app is running on HTTPS a couple of minutes later.
Deploying takes one form and no configuration files.
Steps
- Go to Cloud Apps and choose Deploy app.
- Pick an application from the catalogue. There are over a hundred; the search box filters by name, description and category.
- Choose which subscription it should run in. If you have only one, it is selected for you.
- Choose a name and a subdomain. The subdomain becomes part of your app's address and has to be unique across the platform, so the form checks it as you type.
- Set how much CPU, memory and disk the app may use from the subscription. The defaults are sensible for the app you picked, and the panel will not let you exceed the remaining headroom.
- Deploy.
What happens next
The status moves to Deploying while the images are pulled and the containers are created. Apps that need a database get one created, wired up and given a generated password — you never configure that yourself.
An app with a database restarts a few times on its way up, while it waits for the database to accept connections. That is normal and not a fault.
When the status reaches Running, the app is reachable at its address over HTTPS.
First login
Many apps generate an initial administrator account at deploy. Those credentials are on the app's Credentials tab. Some apps instead ask you to create the first account yourself the first time you open them — in that case, do it promptly, because until you do, anyone who finds the address can.
Still stuck? Get in touch — a person reads every message.