@@ -51,13 +51,32 @@ by editing the `available` check when its first release lands.
5151` aurora.luminusos.org ` is a second build of this same project:
5252
5353``` sh
54- npm run build:aurora # static output in dist- aurora/
55- npm run deploy:aurora # deploy dist-aurora to Cloudflare Pages
54+ npm run build:aurora # static output in aurora/dist /
55+ npm run deploy:aurora # local/manual upload with Wrangler
5656```
5757
5858With ` SITE_VARIANT=aurora ` the Aurora Shell page becomes the site root
5959(` / ` and ` /pt-br/ ` ), cross-links point back to ` https://luminusos.org ` , and
60- ` dist-aurora/CNAME ` is written as ` aurora.luminusos.org ` .
60+ ` aurora/dist/CNAME ` is written as ` aurora.luminusos.org ` .
61+
62+ Cloudflare Pages settings for ` aurora.luminusos.org ` :
63+
64+ | Setting | Value |
65+ | --- | --- |
66+ | Root directory | ` website ` |
67+ | Build command | ` npm run build:aurora ` |
68+ | Build output directory | ` aurora/dist ` |
69+ | Deploy command | leave empty |
70+
71+ The ` deploy:aurora ` script is only for a local/manual Wrangler upload. Do not
72+ use it as the Cloudflare Pages deploy command; Git-connected Pages deployments
73+ upload the configured output directory automatically after the build command.
74+
75+ This repository intentionally does not keep a default ` wrangler.jsonc ` in the
76+ Pages root. The same source tree is used by multiple Cloudflare Pages projects
77+ with different output directories, so each Pages project should use its own UI
78+ settings. The Worker config used by the manual ` npm run deploy ` command lives
79+ in ` wrangler.worker.jsonc ` .
6180
6281## Wiki & Blog (sub-projects)
6382
@@ -80,6 +99,9 @@ npm run build:wiki
8099npm run deploy:wiki
81100```
82101
102+ For Git-connected Cloudflare Pages projects, use only the build command and
103+ output directory. Leave the deploy command empty there as well.
104+
83105## License
84106
85107MIT — see [ LICENSE] ( LICENSE ) .
0 commit comments