Resources

A resource is something your application runs or depends on. Resources live inside an environment and connect to one another through variables.

Kuppit has three kinds of resource:

Every resource has a name that is unique within its environment. The name is how other resources address it in a reference, and for a web service it is also part of the generated hostname.

Adding a resource

On an environment's Overview, choose Add resource — in the navigation bar, on the environment's box, or by right-clicking empty canvas and choosing the environment. Kuppit asks for the kind of resource, how it should be created, and anything that kind needs, then shows a plan to review before anything is provisioned.

A new resource can be created from scratch, or, for a database, cloned from or shared with another environment's database. See PostgreSQL.

Copying a resource to another environment

On the project's Overview, right-click a resource and choose Copy to environment…, then the environment; or drag its card onto that environment's box. Copying is offered for long-lived environments — Production and the ones you name — and a preview cannot take a copy. Either way the card stays where it was, and the same Add resource flow opens on that environment with the resource already chosen as what to start from. What it offers is what that kind allows there: for a database, a clone of its data or a share of the database itself; for a service or a worker, a new one built from that environment's branch. Nothing is created until you review the plan.

A resource is never moved. It belongs to its environment, and a copy is a second resource in another.

From the overview

On the project's Overview, right-click a resource's card, open the ellipsis on it, or select it and use its panel. All three offer the same list, and the list is what that kind of resource can do: Open; Deploy and Redeploy for anything that deploys; View logs; Pause and Resume for a worker; Connect to… a database, for anything that takes variables; How to connect for a database; Copy to environment…; and Delete. Redeploy and Delete ask before anything happens. Nothing is offered that the resource cannot do.

Removing a resource

Deleting a resource is permanent. Choose Delete on the resource's card on the project's Overview, on its panel, or on its Settings tab. A web service loses its deployments, hostnames and history; a worker its deployments and runs; a database loses its data. Kuppit names what will be deleted, and what will merely be disconnected, before you confirm.

A resource shared from another environment is not deleted when removed from this one. The environment simply stops using it.