creght-cli 0.14.0 → 0.16.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/README.md
CHANGED
|
@@ -36,6 +36,8 @@ creght update --check # report versions, install nothing
|
|
|
36
36
|
|
|
37
37
|
The install method is detected, not assumed. A binary vendored by the npm package is updated by running `npm install -g creght-cli@<version>`, so the package's own metadata stays consistent with the binary; a standalone binary is replaced directly with the release archive for the running platform, after its SHA-256 is verified against the release checksums. A local `go build` reports `dev` and is never overwritten.
|
|
38
38
|
|
|
39
|
+
The CLI also keeps itself current. A regular command start spawns this update in the background — at most once per hour — so the command itself is never delayed; the next start runs the new version and prints a one-line notice. Set `CREGHT_NO_AUTO_UPDATE=1` to disable auto-update; the background run logs to `update.log` next to the CLI's `config.json`.
|
|
40
|
+
|
|
39
41
|
## Login
|
|
40
42
|
|
|
41
43
|
For production:
|
|
@@ -253,6 +255,14 @@ paths from `pull`, `diff`, and `push`. Ignored remote files are left untouched,
|
|
|
253
255
|
including when using `push --delete` or `push --force`. The `.creghtignore`
|
|
254
256
|
file itself is always local and is never synced.
|
|
255
257
|
|
|
258
|
+
Order matters: an ignored path also loses its base state, so a rule added
|
|
259
|
+
before the remote copy was deleted leaves that copy live on the site with no
|
|
260
|
+
base for `push --delete` to plan from. `push` and `diff` name the remote files
|
|
261
|
+
a rule is hiding, and `creght rm <path>` deletes one of them. To clear several,
|
|
262
|
+
remove the rule and run `push` to rebuild their base state (`pull` instead if
|
|
263
|
+
the local and remote copies have diverged), delete the files locally, run
|
|
264
|
+
`push --delete`, then add the rule back.
|
|
265
|
+
|
|
256
266
|
The syntax follows common gitignore conventions: blank lines, `#` comments,
|
|
257
267
|
`!` negation, root-relative patterns, directory patterns, and `*`, `?`, and
|
|
258
268
|
`**` wildcards. For example:
|
|
@@ -722,6 +732,7 @@ Command meanings:
|
|
|
722
732
|
- `project`: List available projects and sites. Use `project_id/site_id` with site commands. Also supports `project create`.
|
|
723
733
|
- `pull`: Download site files (including Func code under `backend/func/`) into a local workspace, three-way merging remote and local edits.
|
|
724
734
|
- `push`: Push local workspace changes to the remote site/project after a three-way conflict check.
|
|
735
|
+
- `rm`: Delete one remote site file by path, including a file hidden by `.creghtignore` that `push --delete` cannot reach. Leaves the local copy on disk.
|
|
725
736
|
- `resolve`: List files with conflict markers, or resolve one by keeping the local (`--ours`) or remote (`--theirs`) side.
|
|
726
737
|
- `preview`: Open the remote preview URL for a site in the browser.
|
|
727
738
|
- `publish`: Snapshot the current remote site source into a new version and make it live in one step.
|
package/package.json
CHANGED
|
Binary file
|
package/vendor/darwin-x64/creght
CHANGED
|
Binary file
|
|
Binary file
|
package/vendor/linux-x64/creght
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|