Appearance
Services
A service (a Resource in the control panel) is your own RestoApp server running in the cloud: a RestoApp application with its own database, admin panel and web address. You see and manage only your own resources.
Prototypes
Every service is created from a prototype — a ready-made package that describes what to run and which settings it needs. The settings form you fill in when creating a service comes from the prototype.
The RestoApp prototype has one setting, imageVersion (RestoApp version) — which RestoApp build to run: next (the default, the most recent build) or latest.
Create a service
- Open Resources and press create.
- Enter a Name, for example
my-shop. - In Settings, keep
"imageVersion": "next"or change it to"latest". - Keep RestoApp as the Service (it is chosen for you while it is the only one).
- Press Save.
The location is chosen by the cloud.
The new service is stopped: it does not run and costs nothing until you enable it.
Address
The address is assigned automatically when the service is created and is shown in the URL field right away, for example https://r-1a2b3c4d.dev.resto.cloud. In the Resources list it is a link — use it to open your service once it is online.
The address cannot be changed, and you cannot use your own domain yet.
Lifecycle
A service is started and stopped with the Enabled switch. Status shows where it is:
| Status | Meaning |
|---|---|
stopped | Not running (the initial state) |
starting | Enabled; the server is being set up |
online | Running and reachable at its address |
stopping | Disabled; the server is being removed |
error | Something went wrong — see the status message |
Start
Turn on Enabled. The status changes to starting within a few seconds and then to online. The first start can take up to about 15 minutes; later starts are usually faster.
You can enable a service only if you have enough credits for at least one hour. While a service is enabled, credits are charged for it every hour.
Test mode limit
In the dev cloud you can have at most one enabled service per account. If you enable a second one, it goes to error with the status message Limit: 1 enabled resource per account in test mode. Disable the running one first.
If the status becomes error, read the Status message on the service page — it says what failed (for example, not enough credits, or the server could not start in 25 minutes). The cloud turns Enabled off and removes what was started; to try again, turn Enabled on again.
Stop
Turn off Enabled. The status changes to stopping and then to stopped; your address no longer opens the service, and charging stops.
Data is deleted when you stop a service
In the dev cloud a stopped service keeps no data: its database is removed together with the server. When you enable it again, RestoApp is installed from scratch — with an empty database. The initial administrator password shown in the control panel works again (a password you changed in RestoApp is lost with the data).
Delete
Delete the service in Resources (Actions → Delete). It disappears from the list right away and charging stops; a running server is removed from the cloud within a few minutes.
Sign in to RestoApp
The page of the service in the control panel (Actions → View or Edit) shows the administrator credentials:
| Field | Value |
|---|---|
| Admin login | owner |
| Admin password (initial) | The initial password, generated by the cloud |
Only you, the owner of the service, can see them (and the cloud administrators).
- Open
<your address>/admin, for examplehttps://r-1a2b3c4d.dev.resto.cloud/admin. - Sign in with the login
ownerand the initial password. - On the first sign-in RestoApp opens the About Project wizard: fill in the project details (for example, the city) and press Next. Then you get to the dashboard.
Change the password
We recommend changing the initial password right away. In the RestoApp admin panel:
- Open System → Users and choose
owner. - Fill in Email — it is required to save the user.
- Enter the new password.
- Press Save.
The control panel still shows the initial password afterwards — it is not updated when you change the password in RestoApp. Keep your new password yourself.