Configure multiple Obsidian environments for development, testing, and production. Use when managing separate vaults, testing plugin versions, or establishing a proper development workflow with isolated environments. Trigger with phrases like "obsidian environments", "obsidian dev vault", "obsidian testing setup", "multiple obsidian vaults".
Scanned 9/3/2026
Install to Claude Code
npx -y skills add Dicklesworthstone/pi_agent_rust --skill obsidian-multi-env-setup --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Obsidian Multi Env Setup?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dicklesworthstone-obsidian-multi-env-setup)More formats (shields.io, HTML) on the badges page.
---
name: obsidian-multi-env-setup
description: |
Configure multiple Obsidian environments for development, testing, and production.
Use when managing separate vaults, testing plugin versions,
or establishing a proper development workflow with isolated environments.
Trigger with phrases like "obsidian environments", "obsidian dev vault",
"obsidian testing setup", "multiple obsidian vaults".
allowed-tools: Read, Write, Edit, Bash(mkdir:*), Bash(ln:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
---
# Obsidian Multi-Environment Setup
## Overview
Configure separate development, testing, and production environments for Obsidian plugin development with proper isolation and workflow.
## Prerequisites
- Obsidian desktop app installed
- Plugin development environment set up
- Understanding of symlinks
## Environment Types
| Environment | Purpose | Plugin Source | Data |
|-------------|---------|---------------|------|
| Development | Active coding | Symlinked (live) | Test data |
| Testing | QA/Validation | Built release | Test data |
| Production | Real usage | Community/Release | Real notes |
## Instructions
### Step 1: Create Environment Structure
```bash
#!/bin/bash
# create-obsidian-environments.sh
# Base directory for all environments
OBSIDIAN_ENVS="$HOME/ObsidianEnvs"
# Create environment directories
mkdir -p "$OBSIDIAN_ENVS/development/.obsidian/plugins"
mkdir -p "$OBSIDIAN_ENVS/development/Test Notes"
mkdir -p "$OBSIDIAN_ENVS/testing/.obsidian/plugins"
mkdir -p "$OBSIDIAN_ENVS/testing/Test Notes"
mkdir -p "$OBSIDIAN_ENVS/staging/.obsidian/plugins"
echo "Created Obsidian environments at: $OBSIDIAN_ENVS"
# Create test notes
cat > "$OBSIDIAN_ENVS/development/Test Notes/Welcome.md" << 'EOF'
# Development Vault
This vault is for **active plugin development**.
## Test Content
- [[Link to test]]
- #test-tag
- Regular content
## Frontmatter Test
---
title: Test Note
tags: [development, test]
created: 2024-01-01
---
EOF
cat > "$OBSIDIAN_ENVS/testing/Test Notes/Welcome.md" << 'EOF'
# Testing Vault
This vault is for **QA and validation testing**.
## Test Scenarios
- [ ] Basic functionality
- [ ] Edge cases
- [ ] Performance
- [ ] Mobile compatibility
EOF
echo "Created test notes"
```
### Step 2: Link Plugin to Development Environment
```bash
#!/bin/bash
# link-plugin-dev.sh
PLUGIN_DIR="$HOME/projects/my-obsidian-plugin"
DEV_VAULT="$HOME/ObsidianEnvs/development"
PLUGIN_NAME=$(jq -r '.id' "$PLUGIN_DIR/manifest.json")
# Create symlink for development
ln -sf "$PLUGIN_DIR" "$DEV_VAULT/.obsidian/plugins/$PLUGIN_NAME"
echo "Linked $PLUGIN_NAME to development vault"
echo "Plugin source: $PLUGIN_DIR"
echo "Vault location: $DEV_VAULT/.obsidian/plugins/$PLUGIN_NAME"
```
### Step 3: Configure Environment-Specific Settings
```typescript
// src/config/environment.ts
export type Environment = 'development' | 'testing' | 'production';
export interface EnvironmentConfig {
debug: boolean;
logLevel: 'debug' | 'info' | 'warn' | 'error';
apiEndpoint: string;
features: {
experimental: boolean;
analytics: boolean;
};
}
const configs: Record<Environment, EnvironmentConfig> = {
development: {
debug: true,
logLevel: 'debug',
apiEndpoint: 'http://localhost:3000',
features: {
experimental: true,
analytics: false,
},
},
testing: {
debug: true,
logLevel: 'info',
apiEndpoint: 'https://staging.api.example.com',
features: {
experimental: true,
analytics: false,
},
},
production: {
debug: false,
logLevel: 'error',
apiEndpoint: 'https://api.example.com',
features: {
experimental: false,
analytics: true,
},
},
};
export function getEnvironment(): Environment {
// Detect based on vault name or build mode
if (process.env.NODE_ENV === 'production') {
return 'production';
}
// Could also detect from vault path
return 'development';
}
export function getConfig(): EnvironmentConfig {
return configs[getEnvironment()];
}
```
### Step 4: Testing Vault Configuration
```bash
#!/bin/bash
# setup-testing-vault.sh
TESTING_VAULT="$HOME/ObsidianEnvs/testing"
PLUGIN_DIR="$HOME/projects/my-obsidian-plugin"
# Build release version
cd "$PLUGIN_DIR"
npm run build
# Copy built files (not symlink) to testing vault
PLUGIN_NAME=$(jq -r '.id' manifest.json)
TEST_PLUGIN_DIR="$TESTING_VAULT/.obsidian/plugins/$PLUGIN_NAME"
mkdir -p "$TEST_PLUGIN_DIR"
cp main.js manifest.json "$TEST_PLUGIN_DIR/"
[ -f styles.css ] && cp styles.css "$TEST_PLUGIN_DIR/"
echo "Copied release build to testing vault"
```
### Step 5: Automated Environment Switching
```bash
#!/bin/bash
# obsidian-env.sh - Switch between environments
ENV=$1
BASE_DIR="$HOME/ObsidianEnvs"
case $ENV in
dev|development)
open "obsidian://open?vault=$BASE_DIR/development"
echo "Opening development vault"
;;
test|testing)
open "obsidian://open?vault=$BASE_DIR/testing"
echo "Opening testing vault"
;;
stage|staging)
open "obsidian://open?vault=$BASE_DIR/staging"
echo "Opening staging vault"
;;
prod|production)
echo "Opening production vault (your main vault)"
# Update with your production vault path
open "obsidian://open?vault=$HOME/MyNotes"
;;
*)
echo "Usage: obsidian-env [dev|test|stage|prod]"
exit 1
;;
esac
```
### Step 6: Test Data Generation
```typescript
// scripts/generate-test-data.ts
import * as fs from 'fs';
import * as path from 'path';
const TEST_VAULT = process.env.TEST_VAULT || './test-vault';
interface TestNote {
name: string;
content: string;
frontmatter?: Record<string, any>;
}
const testNotes: TestNote[] = [
{
name: 'Empty Note.md',
content: '',
},
{
name: 'Simple Note.md',
content: '# Simple Note\n\nJust some content.',
},
{
name: 'Note with Links.md',
content: '# Links Test\n\n[[Simple Note]]\n[[Nonexistent Link]]\n\n![[Simple Note]]',
},
{
name: 'Note with Frontmatter.md',
frontmatter: {
title: 'Frontmatter Test',
tags: ['test', 'frontmatter'],
date: '2024-01-15',
nested: {
key: 'value',
},
},
content: '# Frontmatter Test\n\nThis note has frontmatter.',
},
{
name: 'Special Characters !@#.md',
content: '# Special Characters\n\nNote with special chars in filename.',
},
{
name: 'Long Note.md',
content: generateLongContent(1000),
},
];
function generateLongContent(lines: number): string {
const paragraphs = [];
for (let i = 0; i < lines; i++) {
paragraphs.push(`Paragraph ${i + 1}: Lorem ipsum dolor sit amet.`);
}
return '# Long Note\n\n' + paragraphs.join('\n\n');
}
function formatFrontmatter(fm: Record<string, any>): string {
const yaml = Object.entries(fm)
.map(([key, value]) => `${key}: ${JSON.stringify(value)}`)
.join('\n');
return `---\n${yaml}\n---\n\n`;
}
async function generateTestData() {
const notesDir = path.join(TEST_VAULT, 'Test Notes');
fs.mkdirSync(notesDir, { recursive: true });
for (const note of testNotes) {
const content = note.frontmatter
? formatFrontmatter(note.frontmatter) + note.content
: note.content;
const filePath = path.join(notesDir, note.name);
fs.writeFileSync(filePath, content);
console.log(`Created: ${note.name}`);
}
// Create nested folder structure
const folders = [
'Folder A/Subfolder 1',
'Folder A/Subfolder 2',
'Folder B',
'.hidden-folder',
];
for (const folder of folders) {
const folderPath = path.join(TEST_VAULT, folder);
fs.mkdirSync(folderPath, { recursive: true });
fs.writeFileSync(
path.join(folderPath, 'Note.md'),
`# Note in ${folder}\n\nContent.`
);
}
console.log('Test data generation complete!');
}
generateTestData();
```
### Step 7: CI Integration for Environments
```yaml
# .github/workflows/test-environments.yml
name: Test in Multiple Environments
on:
push:
branches: [main]
pull_request:
jobs:
test:
runs-on: ubuntu-latest
strategy:
matrix:
obsidian-version: ['1.4.0', '1.5.0', 'latest']
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Build
run: npm run build
- name: Generate test vault
run: |
mkdir -p test-vault/.obsidian/plugins/my-plugin
cp main.js manifest.json test-vault/.obsidian/plugins/my-plugin/
- name: Run tests
run: npm test
env:
TEST_VAULT: ./test-vault
OBSIDIAN_VERSION: ${{ matrix.obsidian-version }}
```
## Output
- Separate development vault with symlinked plugin
- Testing vault with release builds
- Staging vault for pre-production
- Environment-specific configuration
- Test data generation scripts
- CI integration for multi-version testing
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Symlink not working | Permission denied | Run as admin (Windows) |
| Plugin not loading | Build error | Check main.js exists |
| Wrong environment | Detection failed | Check vault name/path |
| Test data missing | Script not run | Run generate-test-data |
## Examples
### Quick Environment Reset Script
```bash
#!/bin/bash
# reset-test-env.sh
TESTING_VAULT="$HOME/ObsidianEnvs/testing"
# Clear existing data
rm -rf "$TESTING_VAULT/Test Notes"/*
# Regenerate test data
npx ts-node scripts/generate-test-data.ts
# Reinstall plugin
./setup-testing-vault.sh
echo "Testing environment reset complete"
```
### Environment Indicator Component
```typescript
// src/ui/components/env-indicator.ts
import { Plugin } from 'obsidian';
import { getEnvironment } from '../config/environment';
export function addEnvironmentIndicator(plugin: Plugin): void {
const env = getEnvironment();
if (env !== 'production') {
const statusBar = plugin.addStatusBarItem();
statusBar.setText(`[${env.toUpperCase()}]`);
statusBar.addClass(`env-indicator-${env}`);
}
}
```
## Resources
- [Obsidian URI Protocol](https://help.obsidian.md/Extending+Obsidian/Obsidian+URI)
- [BRAT for Beta Testing](https://github.com/TfTHacker/obsidian42-brat)
## Next Steps
For monitoring and logging, see `obsidian-observability`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!