Codeanywhere Migration
Explorer guide for Codeanywhere switchers
Learn how ServerDesk Explorer maps to the file-browsing workflow Codeanywhere users expect after moving to a real server connection.
Confirm the root before editing
The first Explorer task is orientation, not editing. Confirm you are inside the right project root, then expand only the folders you recognise so you do not accidentally work in the wrong environment or site.
Use Open Editors to stay oriented
Open Editors appears below the main file tree and keeps the active working set visible. This is especially helpful during migrations, where you often compare config files, environment files, and framework bootstrap files in quick succession.
Know how different file types behave
Text and code files open in Monaco, images open as previews, SVG files default to preview, and unsupported binary files stay behind a guarded state with download access. This prevents the post-migration confusion of opening a binary asset as broken text.
Need something else?
Move back into the searchable Help Centre, open the Support Hub, or use the public bug report and feature request routes if this article does not cover your workflow.