backend-deployment

Deploy backend services from aramb.toml and return a PUBLIC_URL.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/clode-labs/aramb-skills --skill backend-deployment-clode-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-deployment
Source: https://github.com/clode-labs/aramb-skills/tree/main/backend-deployment
Command: npx skills add https://github.com/clode-labs/aramb-skills --skill backend-deployment-clode-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy backend services by consuming aramb.toml: creates services, builds and deploys images, and returns a PUBLIC_URL for frontend integration. Frontend deployment is managed by the frontend-deployment skill.

Core Features & Use Cases

  • TOML-driven deployment: Creates all services defined in aramb.toml in a single operation.
  • Backend image build & deploy: For services linked to build steps, builds, pushes, and deploys using aramb build --service.
  • PUBLIC_URL extraction: Retrieves the frontend URL for seamless integration with the frontend app.
  • Use case: Bootstrap a multi-service backend (e.g., postgres-db and backend-api) and publish a PUBLIC_URL for the frontend.

Quick Start

From project root, ensure aramb.toml exists and is valid, then run: aramb deploy --deploy-from-toml If build services exist, ensure APPLICATION_ID is set and use aramb build --service to deploy backend components, then retrieve the PUBLIC_URL via aramb deploy status --service <backend-slug>.

Frequently Asked Questions about backend-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate backend deployment from a TOML configuration file?

Automating backend deployment from a TOML file involves consuming aramb.toml to create, build, and deploy services automatically. You run aramb deploy --deploy-from-toml from your project root to orchestrate the entire workflow.

How does building and deploying backend images with aramb work?

Building and deploying backend images with aramb works by using the aramb build --service command for services defined in aramb.toml. This requires setting APPLICATION_ID to derive the application slug and orchestrate the build and deploy process.

What prerequisites do I need to deploy backend services defined in aramb.toml?

To deploy backend services defined in aramb.toml, you need aramb-cli with remote BuildKit configured via BUILDKIT_HOST, a valid aramb.toml in your project root, and APPLICATION_ID set if build services exist.

Can I get a public URL for frontend integration after deploying backend services?

Yes, you can retrieve a public URL for frontend integration after deploying backend services. The workflow extracts a PUBLIC_URL by running aramb deploy status --service <backend-slug>, which the frontend application can then consume.

What is the best way to orchestrate a multi-service backend deployment with Docker?

The best way to orchestrate a multi-service backend deployment with Docker is using a TOML-driven approach. This method creates all services defined in aramb.toml in a single operation, then builds and deploys the backend images for end-to-end orchestration.