obsidian-multi-env-setup

Featured

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".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Obsidian Multi-Environment Setup ## Overview Configure separate development, testing, and production vaults for Obsidian plugin work. Covers vault templates for team onboarding, environment-specific plugin settings, sync strategies, and `.obsidian/` directory management across environments. ## Prerequisites - Obsidian desktop app installed - Node.js 18+ and npm/pnpm for plugin builds - Git for version control (recommended) - Basic understanding of symlinks and file system operations ## Instructions ### Step 1: Create the Environment Structure Set up three isolated vaults -- dev, test, and prod: ```bash # Base directory for all environments mkdir -p ~/obsidian-envs/{dev,test,prod} # Dev vault: your working vault with symlinked plugin source mkdir -p ~/obsidian-envs/dev/.obsidian/plugins/your-plugin mkdir -p ~/obsidian-envs/dev/sandbox # scratch notes for testing # Test vault: clean environment for QA mkdir -p ~/obsidian-envs/test/.obsidian/plugins/your-plugin mkdir -p ~/obsidian-envs/test/test-data # Prod vault: mirrors real user setup mkdir -p ~/obsidian-envs/prod/.obsidian/plugins/your-plugin ``` ### Step 2: Symlink Plugin Source for Development In the dev vault, symlink your plugin's build output so changes appear immediately: ```bash # Remove the empty plugin directory in dev rm -rf ~/obsidian-envs/dev/.obsidian/plugins/your-plugin # Symlink to your plugin's repo (contains manifest.json, main.js, styles.css) ln -s /path/to/your-plugin ~/obsidian-envs/dev/.o...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

obsidian-install-auth

Set up Obsidian plugin development environment with Node.js and TypeScript. Use when starting a new plugin project, configuring the dev environment, or initializing Obsidian plugin development from scratch. Trigger with phrases like "obsidian setup", "obsidian plugin dev", "create obsidian plugin", "obsidian development environment".

2,266 Updated today
jeremylongshore
AI & Automation Featured

obsidian-local-dev-loop

Set up a fast Obsidian plugin development loop with hot reload. Covers cloning the sample plugin, esbuild watch mode, symlinking into a vault, Ctrl+R hot reload, Chrome DevTools debugging, and testing with vitest. Use when starting plugin development or configuring a dev environment. Trigger with "obsidian dev loop", "obsidian hot reload", "obsidian development setup", "develop obsidian plugin".

2,266 Updated today
jeremylongshore
AI & Automation Featured

evernote-multi-env-setup

Configure multi-environment setup for Evernote integrations. Use when setting up dev, staging, and production environments, or managing environment-specific configurations. Trigger with phrases like "evernote environments", "evernote staging", "evernote dev setup", "multiple environments evernote".

2,266 Updated today
jeremylongshore
AI & Automation Featured

juicebox-multi-env-setup

Configure Juicebox multi-environment. Trigger: "juicebox environments", "juicebox staging".

2,266 Updated today
jeremylongshore
AI & Automation Featured

documenso-multi-env-setup

Configure Documenso across multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing API keys, or implementing environment promotion workflows. Trigger with phrases like "documenso environments", "documenso staging", "documenso dev setup", "multi-environment documenso".

2,266 Updated today
jeremylongshore