overleaf/services/history-v1
Antoine Clausse 7f48c67512 Add prefer-node-protocol ESLint rule (#21532)
* Add `unicorn/prefer-node-protocol`

* Fix `unicorn/prefer-node-protocol` ESLint errors

* Run `npm run format:fix`

* Add sandboxed-module sourceTransformers in mocha setups

Fix `no such file or directory, open 'node:fs'` in `sandboxed-module`

* Remove `node:` in the SandboxedModule requires

* Fix new linting errors with `node:`

GitOrigin-RevId: 68f6e31e2191fcff4cb8058dd0a6914c14f59926
2024-11-11 09:04:51 +00:00
..
api Add prefer-node-protocol ESLint rule (#21532) 2024-11-11 09:04:51 +00:00
benchmarks Add prefer-node-protocol ESLint rule (#21532) 2024-11-11 09:04:51 +00:00
config
migrations
storage Add prefer-node-protocol ESLint rule (#21532) 2024-11-11 09:04:51 +00:00
test Add prefer-node-protocol ESLint rule (#21532) 2024-11-11 09:04:51 +00:00
.gitignore
.mocharc.json
.nvmrc
app.js Add prefer-node-protocol ESLint rule (#21532) 2024-11-11 09:04:51 +00:00
buildscript.txt
docker-compose.ci.yml
docker-compose.yml
Dockerfile
knexfile.js
Makefile
package.json
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.