Code Editor

Biztraak Cloud Dev provides a project-connected code environment with an embedded code-server editor, deployment status, logs, and optional terminal access. The exact editor and access options depend on the environment and provider configuration.

Create an environment

1. Open a project and select its code environment workflow.
2. Choose a provider listed for the Cloud Dev environment. See Capabilities and Availability for provider-specific access differences.
3. Create the environment and wait for its deployment to finish.
4. Open the environment from the project when it reports a usable status.

Environment creation provisions cloud resources and can take several minutes. If deployment fails, review the deployment logs before deleting the environment and starting over.

Open the embedded editor

The embedded editor uses code-server. When SSH access is enabled, the UI provides an SSH tunnel command. Run the command in your local terminal, keep the tunnel open, and confirm the connection before opening the embedded editor.

You can also open the editor in a new browser tab over HTTPS when the environment exposes an HTTPS editor URL. HTTPS access may require the temporary code-server password shown by the environment. regenerate it only when necessary and store it securely.

Terminal access

The available terminal options depend on the environment:

• SSH access uses the generated SSH command and the keys configured for the environment.
• The web terminal is available when the environment includes the terminal add-on.
• Cloud-provider terminal integrations may be exposed when the required add-on and instance state are available. See Capabilities and Availability for provider differences.

If SSH or terminal access is disabled, recreate the environment with the required access option enabled. Do not put generated passwords or SSH keys in source code, documentation, or screenshots.

Start, stop, and inspect an environment

Use the environment controls to start or stop a VM-backed environment, adjust its shutdown timer, and review deployment, system, or application logs. Starting an environment does not replace deploying the application or changing the project component configuration.

Current limits

• Editor access requires a ready Cloud Dev environment and an editor URL exposed by that environment.
• The embedded editor requires the environment to be ready and, for SSH mode, an active tunnel.
• Terminal and SSH availability depends on the options selected when the environment was created.
• Provider-specific resource limits, URLs, and runtime behavior may differ.

See Cloud Dev, Virtual Machines, and Environment Variables for related workflows.