Simplified Volume Guide for Sliplane Deployments

Generated: 2025-08-12 UTC
Purpose: Explains the simplified 2-volume layout for Sasha deployments

Overview

The simplified 2-volume layout uses shared volumes across all clients on the same server, dramatically reducing complexity and resource usage while maintaining full functionality.

Simplified Volume Configuration

Two Shared Volumes

Volume	Size	Purpose	Capacity
`nodejs-home`	5Gi	ALL user data, Claude config, projects, workspaces	Substantial content
`sasha-data`	10Mi	SQLite database	Thousands of records

Why This Structure Works

Shared nodejs-home (5Gi)

Contains ALL user data in one place:
- User workspaces at /home/nodejs/workspaces/
- Documentation at /home/nodejs/workspace/docs/
- File uploads at /home/nodejs/uploads/
- Claude projects at /home/nodejs/claude-projects/
- Claude configuration at /home/nodejs/.claude-config.json
- Application config at /home/nodejs/config/
5Gi provides room for:
- 5,000+ documentation pages
- 1,000+ uploaded files (5MB average)
- Complete workspace content
- All Claude projects and configurations

SQLite Efficiency (10Mi for database)

SQLite is incredibly space-efficient
10Mi can store:
- 10,000+ user records
- 50,000+ activity logs
- Complete session management
- All application data for months

Scaling Strategy

When to Scale

Most clients will never need to scale beyond Starter sizing. Consider scaling only when:

Database (10Mi → 100Mi → 1Gi)
- Over 100,000 records
- Heavy analytics workloads
- Multiple years of data
Workspace (5Gi → 10Gi → 20Gi)
- Video content storage
- Large file uploads (>10MB average)
- Extensive documentation (10,000+ pages)
Config (20Mi)
- Never needs scaling

Cost Benefits

Starter vs Traditional Sizing

Volume Type	Traditional	Starter (2Gi)	Savings
Database	1Gi	10Mi	99%
User Data	20Gi	2Gi	90%
Config	500Mi	(included)	100%
Total	21.5Gi	2.01Gi	91%

Growth vs Traditional Sizing

| Volume Type | Traditional | Growth (5Gi) | Savings |
|-------------|------------|--------------|---------||
| Database | 1Gi | 10Mi | 99% |
| User Data | 20Gi | 5Gi | 75% |
| Config | 500Mi | (included) | 100% |
| Total | 21.5Gi | 5.01Gi | 77% |

Monthly Cost Impact

Traditional: Higher storage costs
Starter: Minimal storage costs
Estimated savings: 75-80% on storage fees

Implementation

Via API Deployment (Recommended)

./scripts/deploy-with-api.sh CLIENT_NAME

Automatically creates service-specific volumes:

{service-name}-home: Mounted at /home/nodejs
{service-name}-data: Mounted at /app/data

Manual Configuration

IMPORTANT: Volumes must be defined when creating the service!

When creating a service in Sliplane dashboard:

{service-name}-home: 2Gi starter (or 5Gi for growth)
{service-name}-data: 10Mi

Volume Names

Each service gets its own dedicated volumes:

linzoid-sasha-studio-home & linzoid-sasha-studio-data
hirebest-home & hirebest-data
acme-corp-home & acme-corp-data

NO SHARING between services for security and data integrity!

Best Practices

Start with Starter: Always begin with 2Gi home volume
Service Isolation: Each service gets its own volumes
Monitor Usage: Check actual usage after deployment
Scale Reactively: Only scale when hitting limits
Document Growth: Track when/why scaling occurs
Define at Creation: Remember volumes must be set when creating service

Monitoring Usage

Check Database Size

# SSH into Sliplane
ssh user@your-sliplane-server

# Check database size
du -h /app/data/sasha.db

Check Home Volume Usage

# Check overall usage
df -h /home/nodejs

# Check specific directories
du -sh /home/nodejs/.claude/projects/
du -sh /home/nodejs/uploads/
du -sh /home/nodejs/config/