Draft
Conversation
Introduces backend support for managing VIP Local Dev-Envs through Studio: - Add VIP module with TypeScript types for environments - Implement environment detection by reading instance_data.json - Add Docker-based running status detection - Expose IPC handlers for list, start, stop, and open operations - Add preload API methods for renderer access - Include unit tests with 10 passing tests This enables Studio to detect and manage existing VIP environments created via the VIP CLI, laying the groundwork for UI integration. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The pm2-axon module is imported directly in cli/commands/_events.ts but was not in the Rollup externals list, causing the build to fail with: Rollup failed to resolve import "pm2-axon" from "cli/commands/_events.ts" Adding pm2-axon to the externals list alongside pm2 fixes the build. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add VIP site display in sidebar with running status indicators - Add VIP content tabs (Overview, Settings, Import/Export, Sync) - Add VIP environment start/stop/create functionality - Add VIP context provider for state management - Add "Add VIP Site" option in site creation stepper - Integrate VIP IPC handlers with main process - Extract main content to separate component for cleaner routing
Contributor
|
Thanks for exploration @Crixu . Since it's a proof of concept, I'm adding the "do not merge" label to help us navigate the PR list. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR explores support for detecting and managing VIP Local Development Environments within Studio, allowing developers to have a unified view of all their local WordPress environments.
Key features:
~/.local/share/vip/dev-environment/Technical approach (Hybrid):
Studio acts as a UI layer on top of VIP CLI rather than reimplementing the stack:
instance_data.json)vip dev-env start/stopcommands for lifecycle managementScreenshot
Testing
npm install -g @automattic/vip-clivip dev-env create --slug=test-sitenpm run devChecklist
npm run lint)npm test)