create-avocado-site 0.11.2 → 0.11.4
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/dist/templates/common.js +16 -0
- package/dist/templates/demo-app.js +16 -0
- package/dist/versions.d.ts +1 -1
- package/dist/versions.js +1 -1
- package/package.json +3 -3
package/dist/templates/common.js
CHANGED
|
@@ -195,6 +195,22 @@ EDITOR_CORS_ORIGINS=http://localhost:${config.editorPort}
|
|
|
195
195
|
# SDK warns on the first editor API request. Set both to the same origin.
|
|
196
196
|
NEXT_PUBLIC_EDITOR_ORIGIN=http://localhost:${config.editorPort}
|
|
197
197
|
|
|
198
|
+
# Which loopback origins the orchestrator may fetch server-side.
|
|
199
|
+
#
|
|
200
|
+
# In the standalone and Docker deployments this is the orchestrator's CORS
|
|
201
|
+
# allowlist, which is what the deployment docs describe. In library mode CORS
|
|
202
|
+
# comes from \`corsOrigins\` on the route above, so here the variable has exactly
|
|
203
|
+
# one remaining job: \`publish/diff\` fetches the site's published pages from
|
|
204
|
+
# \`siteOrigin\`, and a private address is refused under NODE_ENV=production
|
|
205
|
+
# unless it is listed here. That check is right — an unchecked loopback value
|
|
206
|
+
# would turn the orchestrator into a proxy onto its own host — but with nothing
|
|
207
|
+
# listed, the production Publish panel answers
|
|
208
|
+
# \`400 siteOrigin is not an allowed URL\` for this site's own origin.
|
|
209
|
+
#
|
|
210
|
+
# On a real deployment the site origin is public and passes without this. It is
|
|
211
|
+
# here because \`npm run build && npm start\` on your own machine is not.
|
|
212
|
+
ORCHESTRATOR_CORS_ORIGINS=http://localhost:${config.sitePort}
|
|
213
|
+
|
|
198
214
|
# Any long random string; this one was generated for you. Without it draft mode
|
|
199
215
|
# does not work, and the editor quietly renders the published page instead of
|
|
200
216
|
# your edits.
|
|
@@ -191,6 +191,22 @@ EDITOR_CORS_ORIGINS=http://localhost:${config.editorPort}
|
|
|
191
191
|
# AVOCADO_EDITOR_ORIGINS only if you run more than one editor deployment.
|
|
192
192
|
NEXT_PUBLIC_EDITOR_ORIGIN=http://localhost:${config.editorPort}
|
|
193
193
|
|
|
194
|
+
# Which loopback origins the orchestrator may fetch server-side.
|
|
195
|
+
#
|
|
196
|
+
# In the standalone and Docker deployments this is the orchestrator's CORS
|
|
197
|
+
# allowlist, which is what the deployment docs describe. In library mode CORS
|
|
198
|
+
# comes from \`corsOrigins\` on the route above, so here the variable has exactly
|
|
199
|
+
# one remaining job: \`publish/diff\` fetches the site's published pages from
|
|
200
|
+
# \`siteOrigin\`, and a private address is refused under NODE_ENV=production
|
|
201
|
+
# unless it is listed here. That check is right — an unchecked loopback value
|
|
202
|
+
# would turn the orchestrator into a proxy onto its own host — but with nothing
|
|
203
|
+
# listed, the production Publish panel answers
|
|
204
|
+
# \`400 siteOrigin is not an allowed URL\` for this site's own origin.
|
|
205
|
+
#
|
|
206
|
+
# On a real deployment the site origin is public and passes without this. It is
|
|
207
|
+
# here because \`npm run build && npm start\` on your own machine is not.
|
|
208
|
+
ORCHESTRATOR_CORS_ORIGINS=http://localhost:${config.sitePort}
|
|
209
|
+
|
|
194
210
|
# This site's public origin. It is the only thing a page cannot work out from
|
|
195
211
|
# its own content, and three tags need it: <link rel="canonical">, og:url, and
|
|
196
212
|
# an og:image resolved to an absolute URL — a relative one is legal in the
|
package/dist/versions.d.ts
CHANGED
|
@@ -17,7 +17,7 @@
|
|
|
17
17
|
* `@avocadostudio-ai/orchestrator-core`, already pinned there; naming it again
|
|
18
18
|
* here is how a project ends up with two.
|
|
19
19
|
*/
|
|
20
|
-
export declare const AVOCADO = "0.11.
|
|
20
|
+
export declare const AVOCADO = "0.11.4";
|
|
21
21
|
/**
|
|
22
22
|
* Next 15.5.15 rather than 16, because that is the version every example app
|
|
23
23
|
* and the demo site in this repository build and test against. The SDK
|
package/dist/versions.js
CHANGED
|
@@ -17,7 +17,7 @@
|
|
|
17
17
|
* `@avocadostudio-ai/orchestrator-core`, already pinned there; naming it again
|
|
18
18
|
* here is how a project ends up with two.
|
|
19
19
|
*/
|
|
20
|
-
export const AVOCADO = "0.11.
|
|
20
|
+
export const AVOCADO = "0.11.4";
|
|
21
21
|
/**
|
|
22
22
|
* Next 15.5.15 rather than 16, because that is the version every example app
|
|
23
23
|
* and the demo site in this repository build and test against. The SDK
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "create-avocado-site",
|
|
3
|
-
"version": "0.11.
|
|
3
|
+
"version": "0.11.4",
|
|
4
4
|
"description": "Bootstrap a runnable Avocado Studio demo site, or wire Avocado into an existing Next.js project",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -34,8 +34,8 @@
|
|
|
34
34
|
"@types/node": "^22.13.10",
|
|
35
35
|
"tsx": "^4.19.0",
|
|
36
36
|
"typescript": "^5.7.3",
|
|
37
|
-
"@avocadostudio-ai/
|
|
38
|
-
"@avocadostudio-ai/
|
|
37
|
+
"@avocadostudio-ai/site-sdk": "0.11.4",
|
|
38
|
+
"@avocadostudio-ai/shared": "0.11.4"
|
|
39
39
|
},
|
|
40
40
|
"license": "Apache-2.0",
|
|
41
41
|
"homepage": "https://docs.avocadostudio.dev",
|