Chrome remote debugging: Difference between revisions
Jump to navigation
Jump to search
(Fix unclosed wikitable: close {|/|} + remove orphan Status; stops sections being swallowed into table) |
(Fix ragged table: pad trailing empty cells so all rows align to full width) |
||
| Line 53: | Line 53: | ||
|} | |} | ||
| | |||
== Best Practices == | == Best Practices == | ||
Revision as of 16:43, 12 October 2026
Overview
Chrome remote debugging에 대한 기술 문서입니다.
Summary
- 무엇인가? - Chrome remote debugging
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: Chrome remote debugging에 대한 기술 정보 제공
- Scope: Chrome remote debugging의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| Chrome remote debugging | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
Chrome Remote Debugging Protocol (CRDP) is a protocol that is used to view and interact with tabs and DevTools of one browser in another browser (probably remote). To develop Webapp on target such as mobile or smart rack system solution RD/RIM by HPCMATE, we open need to access remote running Chrome browser from development host system remotely. cause developers are able to debug remotely running webapp instance on the target system through the Chrome remote debugging environment.
| Where | What | Description |
|---|---|---|
| On target system | Run Chrome with
--remote-debugging-port=9222 --incognito --remote-allow-origins=* |
Chrome on target system support debug port 9222 along with remote-allow-origins |
| Start SSH tunnel
ssh -L 0.0.0.0:9223:localhost:9222 localhost -N |
Enable SSH tunel from 0.0.0.0:9223 to localhost(target):9222.
The reason is Chrome debug port 9222 is only available for localhost(target) | |
| On development system | - Open Chrome URL : http://<Target IP>:9223/ |
|
Best Practices
- 최신 버전 사용 권장
- 공식 문서 참고
- 테스트 환경에서 먼저 검증
References
Related Pages
Knowledge Graph
Related