@demogo-cn/cli 0.2.7 → 0.2.8
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/README.md +3 -1
- package/lib/core.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,7 +6,7 @@ DemoGo CLI lets AI coding tools publish a local project to DemoGo and return a s
|
|
|
6
6
|
|
|
7
7
|
Current MVP delivery uses a local install package.
|
|
8
8
|
|
|
9
|
-
1. Unzip `demogo-cli-v0.2.
|
|
9
|
+
1. Unzip `demogo-cli-v0.2.8.zip`.
|
|
10
10
|
2. Open a terminal in the extracted folder.
|
|
11
11
|
3. Run:
|
|
12
12
|
|
|
@@ -54,6 +54,8 @@ demogo deploy --dir <project-folder> --name <project-name>
|
|
|
54
54
|
|
|
55
55
|
If you only have one HTML file, put that file in a clean folder and publish that folder. You do not need to rename the file to `index.html`.
|
|
56
56
|
|
|
57
|
+
Project names are used for display in the DemoGo workbench. Free accounts receive an automatically assigned trial link path. Paid accounts can receive clearer project link paths, and Pro users can apply for custom access addresses or independent domains.
|
|
58
|
+
|
|
57
59
|
## Current Boundary
|
|
58
60
|
|
|
59
61
|
DemoGo supports static pages, single HTML pages, built frontend output, and frontend source projects that can build static output. It does not host long-running backend services, databases, payment systems, login systems, WebSocket services, or SSR runtimes.
|
package/lib/core.js
CHANGED