genesis-stack 1.2.1 → 1.3.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 +4 -3
- package/package.json +1 -1
- package/stacks/pieces/laravel.md +16 -1
package/README.md
CHANGED
|
@@ -39,7 +39,7 @@ catalog dependency.
|
|
|
39
39
|
|
|
40
40
|
With Genesis 1.4 or newer, `genesis templates list` also lists the JSKIT starters
|
|
41
41
|
in `genesis.templates.json`. Both variants come from
|
|
42
|
-
[
|
|
42
|
+
the [JSKIT seed repository](https://github.com/vibe64-dev/seed-jskit):
|
|
43
43
|
`official:jskit/public` and `official:jskit/accounts`. Apply one to an empty
|
|
44
44
|
Git/Genesis bootstrap project with `genesis templates apply <id>`. Template IDs
|
|
45
45
|
name complete applications; selecting a Skill never silently chooses a starter.
|
|
@@ -103,8 +103,9 @@ are inferred from selecting a language. A project-owned section wins unchanged,
|
|
|
103
103
|
including an explicit different default.
|
|
104
104
|
|
|
105
105
|
For an existing current-format project whose selected catalog gains this
|
|
106
|
-
proposal, Genesis reports
|
|
107
|
-
section
|
|
106
|
+
proposal, the Stack still reads normally and Genesis reports the missing
|
|
107
|
+
section as a pending proposal (`STACK_SECTION_PROPOSALS_PENDING`) until it is
|
|
108
|
+
adopted. Explicitly reconcile the already-selected Stack with
|
|
108
109
|
`genesis stack add <component>`, then review the materialized contract. Older project
|
|
109
110
|
formats use the normal `genesis migrate` workflow. Catalog updates never install
|
|
110
111
|
a hidden runtime default or rewrite an existing project section.
|
package/package.json
CHANGED
package/stacks/pieces/laravel.md
CHANGED
|
@@ -33,7 +33,11 @@ conventions. Authoritative framework documentation: https://laravel.com/docs/
|
|
|
33
33
|
`npm ci` and `npm run build`, optionally `php artisan config:cache` and
|
|
34
34
|
`php artisan route:cache`, then `php artisan migrate --force`, then serves the
|
|
35
35
|
application on the listen address the host supplies. Readiness is `/up`;
|
|
36
|
-
`vendor` and `node_modules` are recreated rather than restored.
|
|
36
|
+
`vendor` and `node_modules` are recreated rather than restored. The proposed
|
|
37
|
+
host-owned `## Deployment` section follows that order and serves through
|
|
38
|
+
`php artisan serve` on the supplied `HOST` and `PORT`, PHP's single-process
|
|
39
|
+
built-in server. Replace its Serve step with the application's production
|
|
40
|
+
server (for example Octane or FrankenPHP) when real traffic needs one.
|
|
37
41
|
- Behind a local reverse proxy, trust only its loopback address (Laravel 11+:
|
|
38
42
|
`$middleware->trustProxies(at: ['127.0.0.1', '::1'])` in
|
|
39
43
|
`bootstrap/app.php`; older versions: `TrustProxies::$proxies`) so `url()`,
|
|
@@ -126,6 +130,17 @@ conventions. Authoritative framework documentation: https://laravel.com/docs/
|
|
|
126
130
|
|
|
127
131
|
- Verify `application`: `php` `artisan` `test`
|
|
128
132
|
|
|
133
|
+
## Deployment
|
|
134
|
+
|
|
135
|
+
- Runtimes: `php` `nodejs`
|
|
136
|
+
- Recreate on restore: `vendor` `node_modules`
|
|
137
|
+
- Ready when: `GET` `/up` returns `200`
|
|
138
|
+
- Prepare `Install PHP dependencies`: `composer` `install` `--no-dev` `--optimize-autoloader` `--no-interaction`
|
|
139
|
+
- Prepare `Install frontend dependencies`: `npm` `ci`
|
|
140
|
+
- Build `Build frontend assets`: `npm` `run` `build`
|
|
141
|
+
- Migrate `Migrate database`: `php` `artisan` `migrate` `--force` `--no-interaction`
|
|
142
|
+
- Serve `Serve`: `sh` `-c` `exec php artisan serve --host="$HOST" --port="$PORT"`
|
|
143
|
+
|
|
129
144
|
## Connected development
|
|
130
145
|
|
|
131
146
|
- Default package type: `composer`
|