overleaf/services/history-v1
Eric Mc Sween b92d1a0251 Merge pull request #16524 from overleaf/em-fix-typescript-backend
Fix typescript config in the backend

GitOrigin-RevId: fb292968bc14da6d7c17bee1da00803a74901899
2024-01-17 09:03:42 +00:00
..
api Merge pull request #15410 from overleaf/jpa-history-v1-verbose-logging 2023-10-25 08:04:54 +00:00
benchmarks
config Merge pull request #15409 from overleaf/jpa-history-v1-http-timeout 2023-10-25 08:04:50 +00:00
migrations
storage Merge pull request #15445 from overleaf/jpa-history-v1-gzip-in-place 2023-10-26 08:03:41 +00:00
test Merge pull request #15382 from overleaf/csh-issue-11625-mongo-ug-5-history-v1 2023-10-26 08:03:38 +00:00
.gitignore
.mocharc.json
.nvmrc Merge pull request #15506 from overleaf/jpa-node-18-18-2 2023-11-01 09:02:48 +00:00
app.js Merge pull request #15409 from overleaf/jpa-history-v1-http-timeout 2023-10-25 08:04:50 +00:00
buildscript.txt Merge pull request #16058 from overleaf/jpa-faster-restart 2023-12-08 09:04:01 +00:00
docker-compose.ci.yml Merge pull request #13060 from overleaf/bg-upgrade-fake-gcs-server 2023-07-24 08:03:58 +00:00
docker-compose.yml Merge pull request #15506 from overleaf/jpa-node-18-18-2 2023-11-01 09:02:48 +00:00
Dockerfile Merge pull request #15506 from overleaf/jpa-node-18-18-2 2023-11-01 09:02:48 +00:00
knexfile.js
Makefile Merge pull request #16524 from overleaf/em-fix-typescript-backend 2024-01-17 09:03:42 +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 Merge pull request #16385 from overleaf/em-typescript-other-services 2024-01-12 09:03:22 +00:00

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.