Templates & Resources
Template recipes and managed resource services
Templates & Resources
Templates
Templates are versioned recipes in the Parslinks catalog that stand up a common stack — a framework starter, an app + database combination, and similar.
Two operations matter:
- Preview — "what would this template create for these inputs?" It creates nothing; the wizard uses it to show you the plan.
- Instantiate — creates real, ordinary resources: a project (if needed), its services, environments, and instances. Instantiation is resumable, so a network hiccup mid-create doesn't leave half a project.
Important: a template is not a special runtime mode. What it creates are completely normal projects and services — you can modify or delete every piece it created afterwards, exactly as if you'd made them by hand.
Resource services
Some services don't run your code. A resource service provides managed
infrastructure to the rest of the project:
| Kind | Examples |
|---|---|
| Managed adapters | PostgreSQL, Redis, message queues — platform-operated, single-replica |
| Brokered plugins | External resources provisioned through a plugin (databases at a cloud provider, etc.) |
Using a resource
- Add the resource service to your project.
- In another service's instance variables, add references to the resource's outputs (host, port, credentials, connection string).
- Redeploy that instance — the referenced values are baked into its new environment snapshot.
Managed adapters run inside the project's private network, reachable via private DNS from sibling services only — never exposed publicly unless you explicitly configure public TCP access.
Choosing between them
- Template: scaffolding many services at once, once.
- Resource service: ongoing infrastructure dependency of your app.