@genex-ai/cli-demo 0.28.0 → 0.29.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -69,6 +69,24 @@ keep its renderer, structure, and conventions — extend, don't rebuild.
|
|
|
69
69
|
Running `genex init` in such a folder only wires identity/publishing and
|
|
70
70
|
refreshes the genex-owned skills; the game's own files are never touched.
|
|
71
71
|
|
|
72
|
+
## Hosting your game's source
|
|
73
|
+
|
|
74
|
+
By default `genex init` creates a **managed repo** for your source — you push to
|
|
75
|
+
it over HTTPS with a token the API mints per push, so it works from any device
|
|
76
|
+
with no SSH key, and `preview`/`publish` save the source there automatically.
|
|
77
|
+
|
|
78
|
+
To keep the source in **your own git repo** instead, pass it at init:
|
|
79
|
+
|
|
80
|
+
```bash
|
|
81
|
+
npx genex init my-game --repo https://git.example.com/you/my-game.git
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
Then `preview`/`publish` push the source to **your** repo using the git
|
|
85
|
+
credentials `git push` already uses on this machine (https or ssh). Point it at a
|
|
86
|
+
repo dedicated to this game — each publish overwrites its `main` with the current
|
|
87
|
+
source. Without push access, publish stops with a clear error and nothing ships.
|
|
88
|
+
The playable game is served by Genex either way.
|
|
89
|
+
|
|
72
90
|
## Publishing
|
|
73
91
|
|
|
74
92
|
Before your first `genex preview`, the play URL (`https://<slug>.genex.technology/`)
|