chore: upgrade impress to v6.0.2 (yhub collaboration), nginx to 1.31.8, docspec 1.21.4
cc-ci/testme cc-ci: failure
cc-ci/testme cc-ci: failure
This commit is contained in:
+4
-13
@@ -1,19 +1,10 @@
|
||||
⚠️ Major upgrade to Docs v6: the collaboration server is replaced by the new `yhub`
|
||||
service, and existing documents have to be migrated to it, or they open EMPTY.
|
||||
|
||||
Before deploying, generate and insert two RSA keys:
|
||||
|
||||
openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:2048 -out jwt.pem
|
||||
openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:2048 -out yhub-jwt.pem
|
||||
abra app secret insert <app-name> jwt_pk v1 jwt.pem -f
|
||||
abra app secret insert <app-name> yhub_jwt_pk v1 yhub-jwt.pem -f
|
||||
|
||||
and add to your app config:
|
||||
|
||||
SECRET_JWT_PK_VERSION=v1 # generate=false
|
||||
SECRET_YHUB_JWT_PK_VERSION=v1 # generate=false
|
||||
|
||||
`SECRET_COLLAB_SS_VERSION` and the `collab_ss` secret are no longer used.
|
||||
`SECRET_COLLAB_SS_VERSION` and the `collab_ss` secret are no longer used. The two
|
||||
RSA keys the backend and yhub sign with are generated automatically on first
|
||||
deploy into the `jwt_keys` volume (the `jwt-keys` service) and reused afterwards;
|
||||
no manual secret insertion is needed.
|
||||
|
||||
After deploying (SOFT_MIGRATION is on by default), migrate all documents:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user