layero 0.8.6 → 0.8.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 +4 -2
- package/dist/pack.js +11 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -80,7 +80,7 @@ Run `layero <cmd> --help` for full options.
|
|
|
80
80
|
- `--name <name>` — project name (only on first deploy).
|
|
81
81
|
- `--project <id_or_slug>` — deploy into an existing project, ignoring
|
|
82
82
|
`./.layero/project.json` (useful for CI).
|
|
83
|
-
- `--prod` — target the production environment of a repository-linked project. **Redundant for CLI projects**: a project created by `layero deploy` auto-promotes to its apex on every deploy, so a plain `deploy` already replaces the live site.
|
|
83
|
+
- `--prod` — target the production environment of a repository-linked project. **Redundant for CLI projects**: a project created by `layero deploy` auto-promotes to its apex on every deploy, so a plain `deploy` already replaces the live site. `--branch` does **not** help here: it is accepted and silently ignored, because every archive upload is filed under the reserved `cli` environment. A publish that leaves the live address alone does not exist for a CLI project — it is done by connecting a repository and pushing to a branch.
|
|
84
84
|
- `--branch <name>` — deploy to a specific branch's environment.
|
|
85
85
|
- `--org <slug>` — Layero organization for first-time project creation.
|
|
86
86
|
- `--yes` / `-y` — non-interactive mode.
|
|
@@ -240,7 +240,9 @@ your agent can react without parsing prose.
|
|
|
240
240
|
|
|
241
241
|
`layero deploy` honours `.gitignore` and `.layeroignore`. The following are
|
|
242
242
|
always excluded: `node_modules`, `.git`, `dist`, `build`, `.next`, `.env*`,
|
|
243
|
-
`.DS_Store
|
|
243
|
+
`.DS_Store`, and the rule files themselves (`.gitignore`, `.layeroignore`) —
|
|
244
|
+
they have no business being on the web, and they list exactly the filenames
|
|
245
|
+
you chose to hide. Maximum archive size is 200 MB.
|
|
244
246
|
|
|
245
247
|
## Config
|
|
246
248
|
|
package/dist/pack.js
CHANGED
|
@@ -25,6 +25,12 @@ const DEFAULT_IGNORE = [
|
|
|
25
25
|
".DS_Store",
|
|
26
26
|
"Thumbs.db",
|
|
27
27
|
".layero",
|
|
28
|
+
// Сами файлы правил на сайте не нужны, а перечисляют они ровно то, что
|
|
29
|
+
// автор прятал: опубликованный `.gitignore` со строкой `private-draft.html`
|
|
30
|
+
// подсказывает, что искать. Проверено на проде — до этой правки оба
|
|
31
|
+
// отдавались с кодом 200. Та же категория, что `.git` и `.env*` выше.
|
|
32
|
+
".gitignore",
|
|
33
|
+
".layeroignore",
|
|
28
34
|
];
|
|
29
35
|
async function readIgnoreFile(filePath) {
|
|
30
36
|
try {
|
|
@@ -146,6 +152,11 @@ export async function packDirectory(targetDir, projectName) {
|
|
|
146
152
|
".DS_Store",
|
|
147
153
|
"Thumbs.db",
|
|
148
154
|
".layero",
|
|
155
|
+
// См. комментарий у DEFAULT_IGNORE: файлы правил перечисляют то, что
|
|
156
|
+
// автор прятал, и на сайте им делать нечего. В каталоге сборки они
|
|
157
|
+
// оказываются редко, но `--prebuilt .` на корне проекта — обычное дело.
|
|
158
|
+
".gitignore",
|
|
159
|
+
".layeroignore",
|
|
149
160
|
]);
|
|
150
161
|
const files = await walk(targetDir, minimalIgnore);
|
|
151
162
|
if (files.length === 0) {
|