overleaf/services/history-v1
Jakob Ackermann 39189978ac Merge pull request #17170 from overleaf/jpa-node-18-19-1
[misc] upgrade Node.js to 18.19.1

GitOrigin-RevId: 1bd2008682b585c3fccc65f74c90ba7fc9edc023
2024-02-20 09:04:55 +00:00
..
api
benchmarks
config Merge pull request #16859 from overleaf/jpa-sharelatex-cleanup 2024-02-09 09:04:11 +00:00
migrations
storage
test [overleaf-editor-core] Restructure TextOperation hierachy (#16582) 2024-01-24 09:04:18 +00:00
.gitignore
.mocharc.json
.nvmrc Merge pull request #17170 from overleaf/jpa-node-18-19-1 2024-02-20 09:04:55 +00:00
app.js
buildscript.txt Merge pull request #17170 from overleaf/jpa-node-18-19-1 2024-02-20 09:04:55 +00:00
docker-compose.ci.yml Merge pull request #17081 from overleaf/csh-build_scripts-redis-acceptance 2024-02-14 09:06:09 +00:00
docker-compose.yml Merge pull request #17170 from overleaf/jpa-node-18-19-1 2024-02-20 09:04:55 +00:00
Dockerfile Merge pull request #17170 from overleaf/jpa-node-18-19-1 2024-02-20 09:04:55 +00:00
knexfile.js
Makefile Merge pull request #17170 from overleaf/jpa-node-18-19-1 2024-02-20 09:04:55 +00:00
package.json Merge pull request #16524 from overleaf/em-fix-typescript-backend 2024-01-17 09:03:42 +00:00
README.md
tsconfig.json

Database migrations

The history service uses knex to manage PostgreSQL migrations.

To create a new migrations, run:

npx knex migrate:make migration_name

To apply migrations, run:

npx knex migrate:latest

For more information, consult the knex migrations guide.

Global blobs

Global blobs are blobs that are shared between projects. The list of global blobs is stored in the projectHistoryGlobalBlobs Mongo collection and is read when the service starts. Changing the list of global blobs needs to be done carefully.

Adding a blob to the global blobs list

If we identify a blob that appears in many projects, we might want to move that blob to the global blobs list.

  1. Add a record for the blob to the projectHistoryGlobalBlobs collection.
  2. Restart the history service.
  3. Delete any corresponding project blobs.

Removing a blob from the global blobs list

Removing a blob from the global blobs list is trickier. As soon as the global blob is made unavailable, every project that needs the blob will have to get its own copy. To avoid disruptions, follow these steps:

  1. In the projectHistoryGlobalBlobs collection, set the demoted property to false on the global blob to remove. This will make the history system write new instances of this blob to project blobs, but still read from the global blob.

  2. Restart the history service.

  3. Copy the blob to all projects that need it.

  4. Remove the blob from the projectHistoryGlobalBlobs collection.

  5. Restart the history service.