create-snagset 0.1.0 → 0.1.1
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/template/README.md +9 -2
- package/package.json +2 -2
package/dist/template/README.md
CHANGED
|
@@ -87,10 +87,17 @@ the widget on one port.
|
|
|
87
87
|
## Upgrading
|
|
88
88
|
|
|
89
89
|
```bash
|
|
90
|
-
pnpm update @snagset/server
|
|
90
|
+
pnpm update @snagset/server --latest
|
|
91
91
|
```
|
|
92
92
|
|
|
93
|
-
Migrations run on boot
|
|
93
|
+
Then `pnpm start` again, or redeploy. Migrations run on boot; there is no
|
|
94
|
+
build step to redo.
|
|
95
|
+
|
|
96
|
+
`--latest` matters: this project pins `@snagset/server` to an exact version on
|
|
97
|
+
purpose (a fresh clone installs the version you last ran), and a plain
|
|
98
|
+
`pnpm update` respects the pin — it does nothing. Back up the database before
|
|
99
|
+
a version that carries migrations; the release notes name any that cannot
|
|
100
|
+
roll back.
|
|
94
101
|
|
|
95
102
|
## Back up your signing key
|
|
96
103
|
|
package/package.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "create-snagset",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.1",
|
|
4
4
|
"private": false,
|
|
5
5
|
"type": "module",
|
|
6
6
|
"description": "Scaffold your own Snagset instance. One command, Postgres included, one variable to fill in.",
|
|
7
7
|
"license": "AGPL-3.0-only",
|
|
8
8
|
"bin": {
|
|
9
|
-
"create-snagset": "
|
|
9
|
+
"create-snagset": "dist/index.js"
|
|
10
10
|
},
|
|
11
11
|
"scripts": {
|
|
12
12
|
"typecheck": "tsc -p tsconfig.json --noEmit",
|