Installers

Identity

What this installer is and where it lives: its service, its server, its owner and its state.

You can

• Read State for how its last run went, from Draft before its first install to Deployed, Error or Deleted.
• Click Server to open the server it runs on.
• To run the service on another server, or another service on this one, install it there (Installing a service).

Good to know

• Nothing in this section can be changed.
• Deploy Queue means a run waits or runs; Delete Queue means the service is being uninstalled.
• CloudWady names the installer after its server's project and environment and the service.
• Code is the short name of its folder, its container and its address on the server.

Deployment & Routing

How the service is deployed on its server, and how traffic reaches it.

You can

• Pick another Domain Provider, the domain its address and DNS records are made under, until the installer is first installed.
• On Coder, pick the Registry Account its image is pulled with. Coder needs one.
• On Coder with the CloudWady login, get the Terminal sudo password from the section's title row, after you confirm your own password.

Good to know

• Press Save to keep a change; the next Deploy or Update uses it.
• After the first install the domain provider is fixed, because the address and DNS records stay under it.
• Load Balancer comes from the server. Certificates, Platform Session Login, Start on Demand and SSH Tunnel Access need Traefik.
• Changing these takes Developer Plus on a development or staging server, Maintainer on a production one.
• The sudo password only serves sudo in Coder's terminal, and showing it takes Developer or above.

Linked Projects

The projects that use this service: every project with an environment on its server.

You can

• Click a project to open it.
• See which projects an Update or Uninstall here reaches before you run one.

Good to know

• The service is shared: an Update or Uninstall here affects every project listed.
• The list follows the server; you do not edit it here.
• The section is hidden when no project uses the server, for example on a server that holds only services.

Access

How people reach the service besides its address: through a tunnel, with their CloudWady login, and only while it is used.

You can

• Turn on SSH Tunnel Access to also put the service on its server's loopback address, for an SSH tunnel (SSH tunnel access).
• On Coder and pgAdmin, turn on Platform Session Login so people open it with their CloudWady login. Off, pgAdmin asks for its own password and takes no apps.
• On Coder and pgAdmin, turn on Start on Demand so it runs only while used. A pgAdmin installed from an app's Access menu has it on.
• Pick how long it stays up unused with Stop When Idle For: 15 minutes unless you change it, up to 2 hours.

Good to know

• A saved change reaches the server on the next Update. It takes Developer Plus on a development or staging server, Maintainer on a production one.
• Platform Session Login is greyed out unless the server runs Docker behind Traefik with the platform's sign-in set up.
• With the login on, Coder lets in whoever may open a terminal on its server, and pgAdmin whoever added an app with two-factor sign-in (Connections).
• Asleep, its address shows a page saying so and its certificate keeps renewing. Open, Deploy or Update starts it in up to a minute.
• Any traffic or open connection, even an open tab, keeps it awake. When Coder stops, everything in it stops too, terminals and builds included.

Settings

The settings this service offers, with this installer's values: its limits, its version and what else it allows.

You can

• Cap its container with Memory Limit and CPU Limit, on most services.
• Pin a version in Image Tag, where the service offers one, to decide when it upgrades.
• Set the other options it offers, such as how long it keeps its data, then press Save.
• Leave a field empty to take the service's default, which the field shows greyed.

Good to know

• Saved values reach the server on the next Update.
• CloudWady checks every value first: when one is refused, nothing on the screen is saved and the message says why.
• A setting that holds a secret, such as an admin password, is stored encrypted and shows only whether it is set: the eye beside it shows it once you confirm your password. It is chosen when the service is installed.
• Changing settings takes Developer Plus on a development or staging server, Maintainer on a production one. Everyone else only sees the values.

Traefik Dashboard

Where Traefik's own dashboard, which shows the routes of every app on this server, answers and who may reach it.

You can

• Copy the dashboard's address from Dashboard URL; Dashboard User is the user name it asks for.
• Let more addresses reach it in Allowed CIDRs, separated by commas, such as 203.0.113.10/32, then press Save.

Good to know

• With Allowed CIDRs empty, the dashboard answers only from the server itself. It always asks for the user and its password.
• An address that is not a valid IP or CIDR is refused when you save.
• The change reaches Traefik on the next Update, which restarts Traefik for every app on the server.
• Changing these takes Developer Plus on a development or staging server, Maintainer on a production one.
• The dashboard's password stays with CloudWady staff.

Connections

The apps people added to their own pgAdmin on this server, and whether each connection still works.

You can

• Read each row's State. On Prepare again, the read role's password changed: add the app again from its screen.
• Take an app out of a person's pgAdmin with Remove from pgAdmin, once you confirm.
• Add an app from its own screen with Access → Add to My pgAdmin (The Access menu).

Good to know

• Each app connects as its read role, so pgAdmin only reads its database.
• Adding an app takes the right to reveal its read role: the namespace's Maintainers and Admins.
• You see your own rows; a namespace's Maintainers and Admins see, and may remove, every row of its apps.
• No longer allowed means the person lost the right, for example their level changed or two-factor sign-in went off. CloudWady takes those out itself.
• Removing drops the connection and the password pgAdmin used, and the app's history notes who did it. The person can add it again while allowed.

Certificates

Who issues the TLS certificates of this installer's addresses.

You can

• Pick the Certificate Provider: Let's Encrypt, the default, or Buypass.
• Confirm a new provider with Change and re-issue.

Good to know

• The change does not wait for Save: it is stored at once, and a route refresh issues every certificate again.
• Until each certificate is issued again, visitors may see a certificate warning.
• One provider serves every address of the installer; you cannot pick one per address.
• The choice is locked while the installer has a run going.
• Changing it takes Developer Plus on a development or staging server, Maintainer on a production one.

URLs

The addresses this installer answers on, with each one's route, certificate and latest run.

You can

• Add one of your own domains with Add Custom URL: enter the domain only, without https://.
• Edit an address, or check its certificate, with the buttons on its row.
• Use a row's … menu for Refresh Route, Retry Latest Workflow, Mark for Deletion (or Restore) and Delete Now.
• Read the columns as on an app's URLs (URLs and certificates).

Good to know

• Point the domain's DNS at the server before you add it.
• The starred address is the default one, made from the domain provider; it cannot be changed.
• A deployed address cannot be renamed: add the new one, then delete the old one.
• You only see the actions you may use.

Coder

Coder is a code editor that runs on your server. Once it is installed, the environment's toolbar has a Coder button that opens the editor in its own window; before that, the button installs it. With Platform Session Login on, in the installer's Configs → Access, you sign in with your CloudWady login, if you may open a terminal on the server. Coder's password then only serves sudo in its terminal: get it with Terminal sudo password, under Deployment & Routing on the installer's Overview.

pgAdmin

pgAdmin signs you in with your CloudWady login and lists the apps you added to it, each connected as the app's read role. Add an app from its screen with Access → Add to My pgAdmin, then open it with Open pgAdmin. It needs two-factor sign-in, which you turn on in My Settings, and the right to reveal the app's read role, which a namespace's Maintainers and Admins have. See Connections.