| … | … | @@ -106,8 +106,8 @@ The `file:` edges that make this exact set mandatory: |
| 106 | 106 | - **hyper-svc** → hyper-rooms |
| 107 | 107 | - **pgh-runtime** → hyper-overlay |
| 108 | 108 | |
| 109 | | Clone all eight over the forge (HTTPS anonymous read; substitute your own |
| 110 | | mirror for `7rnx.net` if you have one): |
| 109 | Clone all eight from the forge over **HTTPS** (anonymous read; substitute your |
| 110 | own mirror for `7rnx.net`): |
| 111 | 111 | |
| 112 | 112 | ```bash |
| 113 | 113 | mkdir -p pgh-src/repos && cd pgh-src |
| … | … | @@ -119,8 +119,12 @@ done |
| 119 | 119 | git clone https://7rnx.net/git/hyperident.git repos/hyperident |
| 120 | 120 | ``` |
| 121 | 121 | |
| 122 | | (Already running a forge? `git clone punch://<serverKey>/<repo>` works too, |
| 123 | | once `git-remote-punch` is installed.) |
| 122 | **Why HTTPS and not the native `punch://` transport?** This is a bootstrap: |
| 123 | `git clone punch://<serverKey>/<repo>` needs `git-remote-punch`, which is |
| 124 | itself a pgh app (`pgh app install git-remote-punch`) — so it isn't available |
| 125 | until pgh is up. Plain HTTPS is the only way in before you have the stack. Once |
| 126 | pgh is running, `punch://` is the preferred P2P transport for cloning anything |
| 127 | else. |
| 124 | 128 | |
| 125 | 129 | ### 3. Install dependencies (leaf packages first) |
| 126 | 130 | |