Codeanywhere Migration
Terminal guide for Codeanywhere switchers
Use the browser terminal to validate your migrated project path, inspect services, and troubleshoot safely after the move.
Your first commands
Start with `pwd`, `ls -la`, and any low-risk project checks that confirm you are in the right directory. This re-establishes confidence quickly after leaving a hosted workspace.
Use logs and status checks before changes
When something looks wrong after migration, read before you write. Check service logs, process state, framework output, or Docker logs before you restart services or edit configuration.
Bring Robbie in for interpretation
If the terminal output is unfamiliar, ask Robbie to explain the error or summarize likely causes. That keeps the migration moving without guessing at stack traces, framework noise, or system-service errors.
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.