Skip to main content

Dev Environments

Dev Environments give you a full VS Code in the cloud — any framework, full control over the runtime, and zero local setup. Powered by code-server and running entirely within MINEO's infrastructure, they let you code, debug, and test directly in the browser with full access to your project files.

Key Benefits:

  • Zero local setup: Start coding instantly from any browser, on any machine
  • Project file access: Your project's filesystem is mounted and ready to use
  • Consistent environments: Every team member works in the same configured environment
  • Resource flexibility: Choose CPU, RAM, and GPU allocations that match your workload
  • Auto-hibernation: Environments hibernate automatically after inactivity to save resources
  • Persistent settings: Optional user data and extensions directories preserve your VS Code configuration across sessions

Quick start​

  1. Go to Project Settings → Dev Environments
  2. Click the + button to create a new dev environment
  3. Give it a name and select a working directory
  4. (Optional) Set a User data directory to persist VS Code settings and extensions
  5. (Optional) Set an Extensions directory for custom VS Code extensions
  6. Choose a Worker Image from the predefined images available for dev environments
  7. Select a Worker environment (CPU, RAM, GPU) that fits your workload
  8. Click OK to create
  9. Once the status shows Running, click Open to launch VS Code in your browser

Opening files in Dev Environments​

Once a dev environment is running, you can open your project files directly in VS Code without leaving the file explorer:

From the file explorer​

Right-click on any File or Folder and use the Dev environment submenu:

OptionDescription
Open with defaultOpens the file/folder in the project's default dev environment.
Open with other...Opens a modal to select which dev environment to use.

Files open in the VS Code editor, while folders open as the working directory in the VS Code file explorer.

From the built-in file editor​

When editing a file in the built-in editor, the toolbar includes an Open in dev environment button. Clicking it opens a menu with the same two options described above. This lets you switch from the lightweight editor to the full VS Code environment at any time.

How dev environments work​

Optional persistent directories​

User data directory​

The User Data Directory stores your personal VS Code configuration that persists across dev environment sessions. When you specify a user directory within your project, the following data will be preserved:

  • VS Code settings (themes, keybindings, UI preferences)
  • Installed extensions (user-installed extensions remain available)
  • Keyboard shortcuts and customizations
  • Git credentials and user data
  • Snippets and user-created code templates

Note: Alternatively you can store settings and preferences on your workspace settings. Which will be under your working directory under the .vscode folder. Use those workspace settings for project specific settings that should be shared with other team members.

Extensions directory​

The Extensions Directory allows you to pre-install and persist VS Code extensions separately from the base worker image. This is useful when:

  • You need extensions not included in the default worker image
  • Your team requires specific extensions for your project
  • You want to version-control your extension set

Usage: Specify a project directory (e.g., /extensions) where extensions will be installed and persisted.

Note: Extensions installed via the Extensions Directory take precedence over those in the User Data Directory for consistency across environments.

Lifecycle​

  1. Create: Define a dev environment with a name, working directory, and resource configuration
  2. Configure (Optional): Set persistent directories for user data and extensions
  3. Run: MINEO provisions a cloud container with VS Code, your project files, and any persistent directories
  4. Code: Open the environment in your browser and work as you would in a local VS Code with your personalized settings
  5. Hibernate: After a period of inactivity, the environment hibernates automatically to save resources
  6. Resume: Opening a hibernated environment wakes it up automatically, restoring your previous session including settings and extensions

Best practices​

  • Team consistency: Commit workspace settings to version control so all team members share the same development environment setup, but not user or extensions dir.
  • Project-specific configurations: Use different persistent directories for different projects to maintain isolated environments
  • Resource management: Larger extension sets may increase environment startup time; balance convenience with performance needs
  • Security: Be cautious with persisted Git credentials and sensitive data in User Data directories

See also​

  • Worker Images — the predefined runtime images you select when creating a dev environment.
  • Live Apps — publish and serve interactive apps from your project.
  • Pipelines — orchestrate and schedule data workflows.
  • File system — browse, edit, and manage the project files mounted into your dev environment.