Working from your editor: VS Code, PhpStorm, Sublime

There is no Orax extension to install in any editor. Everything needed to work on a site hosted with us is already in VS Code, PhpStorm and Sublime Text — all that is missing is access, configured once.

One setup for every editor

Your service's "Access and passwords" page carries a ready block for ~/.ssh/config. Add it to your machine once and the connection works everywhere at once: in any editor, in the terminal, in scp, rsync and git. After that a short name like orax-c123 replaces the host, the port and the login.

The site folder is shown there too — usually www/your-domain. Every editor asks for it when you set up remote work.

Connect with an SSH key rather than a password: keys are added under "SSH keys" on your service.

Phpstorm

Almost everything is built in here; no plugins needed.

• Files: Settings → Build, Execution, Deployment → Deployment, add an SFTP server, give it the host from your config and the site folder. Turn on Automatic upload and edits leave on save.
• Terminal: Tools → Start SSH Session.
• Database: the Database tab → MySQL, host localhost, port 3306, and on the SSH/SSL tab enable a tunnel through the same access. The database login and password are in the service's Databases section. The database then opens inside the editor without being exposed to the internet.

Vs code

• Microsoft's Remote - SSH extension: connect to the host from your config and open the site folder as an ordinary project. Editor, terminal and debugger behave as if the code were on your own machine.
• If memory is tight, use any SFTP extension instead — upload on save, almost no resource cost. Remote-SSH starts a process of roughly 100 MB inside your account; our plans begin at 1 GB, so there is room, but it is your memory.

Sublime text

There is no remote development as such, but there is the SFTP package: create sftp-config.json in the project folder with the host, user, port and site folder, and files go to the server on save.

Deploying from git

Independent of the editor entirely. Your service page has a Git section: link a repository and every push to the chosen branch publishes the code.

• The first deploy lays the branch over the site folder: files from the repository are overwritten, everything else stays — your uploads are not deleted.
• Later deploys bring the folder to match the branch.
• You can give a build command; it runs after the files land.

The ai sees your account

It connects over the MCP standard with a single address: https://orax.uz/api/v1/mcp. The agent can talk about your services, their dates, your balance and whether the site is up, but will not order or pay for anything — details in the article on connecting an AI.

• Claude Code: claude mcp add --transport http orax https://orax.uz/api/v1/mcp
• VS Code: a .vscode/mcp.json file with the same address.

Which to choose

• Editing live and seeing the result at once — Remote-SSH in VS Code or Deployment in PhpStorm.
• Code in a repository, releases by push — Git deploy.
• Dropping a couple of files — SFTP or the cabinet's file manager.
• Asking an AI about your account — MCP.

None of these excludes the others: you can have all of them at once.