migrateDB script missing in package.json in the official container image

[s3lph]

Describe the bug
In the official Etherpad Lite container image, the migrateDB script described in the documentation is reported as missing.

To Reproduce
Steps to reproduce the behavior:

1. Start Etherpad Lite in a container using the official docker.io/etherpad/etherpad:2.4.2 image.
2. Open a shell to the container e.g. using docker/podman exec -it etherpad bash,
3. Create the old and new db config JSON files and run pnpm run migrateDB --file1 old.json --file2 new.json
4. Receive the following error message: Missing script: migrateDB

Expected behavior
The database migration should start as described in the CLI documentation.

Screenshots

d949719b2397:/opt/etherpad-lite$ pnpm run migrateDB --file1 old.json --file2 new.json
 ERR_PNPM_NO_SCRIPT  Missing script: migrateDB

Command "migrateDB" not found.

**Server

• Etherpad version: 2.4.2
• OS: Alpine Linux v3.22 (Official container image)
• Node.js version (node --version): v22.17.1
• npm version (npm --version): 10.9.2
• Is the server free of plugins: Yes, using the official docker.io/etherpad/etherpad:2.4.2 image.

Additional context
The script is present in /opt/etherpad-lite/bin/migrateDB.ts, but is missing from the scripts section of /opt/etherpad-lite/package.json. It can still be invoked using pnpm --filter bin run migrateDB --file1 old.json --file2 new.json:

d949719b2397:/opt/etherpad-lite$ pnpm --filter bin run migrateDB --file1 old.json --file2 new.json

> bin@2.4.2 migrateDB /opt/etherpad-lite/bin
> node --import tsx migrateDB.ts --file1 old.json --file2 new.json

...

[SamTV12345]

Hi @s3lph I didn't want to clutter the main namespace of etherpad. You can still do this without an issue by going to /opt/etherpad-lite/bin and execute the command. Of course you would need to adapt the paths if the json files are in the root directory of etherpad-lite. Hope this helps :)

[s3lph]

@SamTV12345 thanks for your quick response.

If this is indeed intended behavior, then I would argue the documentation needs updating to reflect this behavior.

[IamSinghYuvraj]

Describe the bug In the official Etherpad Lite container image, the migrateDB script described in the documentation is reported as missing.

To Reproduce Steps to reproduce the behavior:

1. Start Etherpad Lite in a container using the official docker.io/etherpad/etherpad:2.4.2 image.
2. Open a shell to the container e.g. using docker/podman exec -it etherpad bash,
3. Create the old and new db config JSON files and run pnpm run migrateDB --file1 old.json --file2 new.json
4. Receive the following error message: Missing script: migrateDB

Expected behavior The database migration should start as described in the CLI documentation.

Screenshots

d949719b2397:/opt/etherpad-lite$ pnpm run migrateDB --file1 old.json --file2 new.json
 ERR_PNPM_NO_SCRIPT  Missing script: migrateDB

Command "migrateDB" not found.

**Server

• Etherpad version: 2.4.2
• OS: Alpine Linux v3.22 (Official container image)
• Node.js version (node --version): v22.17.1
• npm version (npm --version): 10.9.2
• Is the server free of plugins: Yes, using the official docker.io/etherpad/etherpad:2.4.2 image.

Additional context The script is present in /opt/etherpad-lite/bin/migrateDB.ts, but is missing from the scripts section of /opt/etherpad-lite/package.json. It can still be invoked using pnpm --filter bin run migrateDB --file1 old.json --file2 new.json:

d949719b2397:/opt/etherpad-lite$ pnpm --filter bin run migrateDB --file1 old.json --file2 new.json

> bin@2.4.2 migrateDB /opt/etherpad-lite/bin
> node --import tsx migrateDB.ts --file1 old.json --file2 new.json

...