Skip to content

Commit

Permalink
run migration docs (#114)
Browse files Browse the repository at this point in the history
* run migration docs

* mentioned DB_ENGINE related stuff for migration

* minor changes

* added upgrade guide for v1.14.0

---------

Co-authored-by: Deepak Prabhakara <[email protected]>
  • Loading branch information
ukrocks007 and deepakprabhakara authored Oct 14, 2023
1 parent 9d19e80 commit 8fd9633
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 1 deletion.
11 changes: 11 additions & 0 deletions docs/jackson/deploy/env-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,17 @@ If you are using a self-signed certificate then set this to `false`, otherwise i

Default: `true`

### **DB_MANUAL_MIGRATION**

Set this to true to trigger execution of migration scripts when you use our Jackson docker image.

Optionally you can run the npm scripts present in `./npm/package.json` to run db specific migrations.

Make sure you have set the correct value for `DB_ENGINE` environment variable as the migration script checks that to run correct command and migration file.

NPM library option: `db.manualMigration`
Default: `false`

### **DB_TTL**

TTL for the code, session and token stores (in seconds)
Expand Down
6 changes: 5 additions & 1 deletion docs/jackson/upgrade.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,12 @@
# Upgrade Guide

## Upgrading to v1.14.0

We have changed the schema bit to introduce a new column called `namespace` to speed up scans. You will have to run the migration scripts if you are manually managing migrations. For example PlanetScale where auto migrations are not supported due to a difference between MySQL and PlanetScale.

## Upgrading to v1.11.0

We have patched the SSO connection (`/api/v1/connections`) DELETE handler to accept payload (client/Secret or tenant/product/strategy) as part of query parameters. Earlier, the payload was expected to be part of the body which is non-standard and is no longer supported in Next.js.
We have patched the SSO connection (`/api/v1/connections`) DELETE handler to accept payload (client/Secret or tenant/product/strategy) as part of query parameters. Earlier, the payload was expected to be part of the body which is non-standard and is no longer supported in Next.js.

## Upgrading to v1.9.7

Expand Down

0 comments on commit 8fd9633

Please sign in to comment.