accessories

Manage lifecycle of accessory services like databases and caches in Kamal deployments.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/donnfelker/kamal-skills --skill accessories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessories
Source: https://github.com/donnfelker/kamal-skills/tree/main/skills/accessories
Command: npx skills add https://github.com/donnfelker/kamal-skills --skill accessories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill simplifies the deployment and lifecycle management of long-lived background services like databases, caches, and search engines that are essential to your application but operate outside the standard Kamal deployment flow.

Core Features & Use Cases

  • Lifecycle Management: Provides commands to boot, reboot, restart, and remove accessory containers independently of your main application deployment.
  • Configuration Mapping: Facilitates the mapping of host volumes, environment variables, and secrets to ensure persistent data and secure credential handling.
  • Use Case: When your application requires a dedicated Redis cache or MySQL database, use this skill to define the accessory in your configuration and safely manage its state across server reboots.

Quick Start

Use the accessories skill to boot the mysql service defined in your configuration file.

Frequently Asked Questions about accessories

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

FAQPage Schema
How do I manage long-lived database and cache services in a Kamal deployment?

You can manage long-lived accessory services in Kamal by using explicit boot, reboot, and removal commands to control Docker containers like databases and caches independently from your main application deployment.

How do I boot a Redis or MySQL accessory container independently of my main application?

Boot a Redis or MySQL accessory container independently by defining it in your Kamal configuration and issuing an explicit boot command to start the Docker container with its mapped host volumes and secrets.

Does Kamal accessory management support persistent volumes and environment variables for Docker containers?

Kamal accessory management supports persistent volumes and environment variables by facilitating the mapping of host volumes and secrets to ensure persistent data and secure credential handling for Docker containers.

What is the best way to remove or restart a database container without redeploying the entire Kamal application?

The best way to remove or restart a database container without redeploying the entire Kamal application is to use explicit reboot and removal commands designed to safely control accessory container lifecycles independently.

When do I need to configure accessory services separately from my standard Kamal deployment flow?

You need to configure accessory services separately from the standard Kamal deployment flow when your application requires long-lived background services like databases or caches that operate independently and must survive server reboots.