@vibedropio/publisher 0.22.2 → 0.22.3
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.
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "git-publisher",
|
|
3
3
|
"displayName": "Git Publisher",
|
|
4
|
-
"version": "0.22.
|
|
4
|
+
"version": "0.22.3",
|
|
5
5
|
"description": "Publish an app folder to the platform and keep it updated (\"publish my app\", \"update my app\", \"fetch the engineered version\").",
|
|
6
6
|
"author": { "name": "VibeDrop" },
|
|
7
7
|
"keywords": ["git", "publish", "deploy", "serverless"]
|
|
@@ -116,6 +116,12 @@ you write the app, the platform prepares its hosting, so the first publication g
|
|
|
116
116
|
seconds, not in a minute. The folder must exist, and it can be empty. Its output names the app
|
|
117
117
|
under `appId`. Then write the app into that folder, and publish it with step 3, without `--name`.
|
|
118
118
|
|
|
119
|
+
`placement` in the output says where the app runs. When `placement.refused` is `"must-pick"`, the
|
|
120
|
+
first publication stops until the person picks one of `placement.offered` on the Cell tab of the
|
|
121
|
+
app in the portal. When it is `"no-cell"`, an owner or admin can give them a cell. Tell them, and
|
|
122
|
+
do not run `init` again: that makes a second app. When the person names a cell before you make the
|
|
123
|
+
app, add `--cell <cell>` to `init`.
|
|
124
|
+
|
|
119
125
|
If the app is already written and was never published, `init` gains nothing. Run step 3 in the
|
|
120
126
|
app folder and add `--name "<app name>"`: that one `sync` makes the app, and then publishes it.
|
|
121
127
|
|