Min Idzelis 54bc9ddd69
chore: add vitest project names and fix server config root paths (#26684)
Add `name` to all vitest configs matching CI job buckets (server:unit,
server:medium, cli:unit, web:unit, e2e:server, e2e:maintenance) so they
appear as filterable @tags in the Vitest VSCode extension.

Fix `root` in server vitest configs to use an absolute path derived from
`import.meta.url` instead of `'./'`, which resolved relative to the config
file directory (`server/test/`) rather than `server/`, causing test
discovery to fail in the Vitest VSCode extension.
2026-03-04 08:20:43 -05:00
..
2025-07-01 08:00:41 -04:00
2023-07-06 09:37:47 -05:00
2023-12-18 20:29:26 -06:00
2024-03-14 13:09:27 -04:00
2024-01-12 07:36:27 -05:00
2024-02-12 15:31:59 +00:00
2025-11-10 15:55:15 +01:00

A command-line interface for interfacing with the self-hosted photo manager Immich.

Please see the Immich CLI documentation.

For developers

Before building the CLI, you must build the immich server and the open-api client. To build the server run the following in the server folder:

$ pnpm install
$ pnpm run build

Then, to build the open-api client run the following in the open-api folder:

$ ./bin/generate-open-api.sh

Run from build

Go to the cli folder and build it:

$ pnpm install
$ pnpm run build
$ node dist/index.js

Run and Debug from source (VSCode)

With VScode you can run and debug the Immich CLI. Go to the launch.json file, find the Immich CLI config and change this with the command you need to debug

"args": ["upload", "--help"],

replace that for the command of your choice.

Install from build

You can also build and install the CLI using

$ pnpm run build
$ pnpm install -g .