missing cargo lock

Hi, The documentation on how to start the project have a small error, if I try to clone the repository and run `docker-compose up --build`, I get this: ```sh ❯ docker-compose up --build [+] Running 23/23 ✔ redis Pulled 6.0s ✔ efc2b5ad9eec Already exists 0.0s ✔ 82797145fff6 Pull complete 0.8s ✔ 405e1ffae71e Pull complete 0.8s ✔ 0beb16fe974a Pull complete 1.0s ✔ 73eb92ddeed3 Pull complete 3.1s ✔ 87e613039f4a Pull complete 3.1s ✔ 4f4fb700ef54 Pull complete 3.1s ✔ 9579b898bbe4 Pull complete 3.2s ✔ db Pulled 22.6s ✔ b33c47d38f22 Pull complete 2.9s ✔ 87cb89a22d1e Pull complete 4.2s ✔ fd66d978bf1a Pull complete 4.2s ✔ d1723030f70f Pull complete 5.1s ✔ 4ed8886da429 Pull complete 5.2s ✔ 2c0a96a00eeb Pull complete 5.2s ✔ 224e967d7685 Pull complete 5.5s ✔ 4774bf58af6a Pull complete 19.5s ✔ 5f45270309c1 Pull complete 19.6s ✔ 60cb0fc6dcac Pull complete 19.6s ✔ abcf585d57b0 Pull complete 19.6s ✔ 87cb29313a81 Pull complete 19.6s ✔ 2e7f0c5387bd Pull complete 19.7s [+] Building 2.7s (10/26) docker:orbstack => [backend internal] load build definition from Dockerfile 0.1s => => transferring dockerfile: 1.72kB 0.0s => [backend internal] load metadata for docker.io/library/rust:1.75-slim-bullseye 2.4s => [backend internal] load metadata for docker.io/library/debian:bullseye-slim 2.4s => [backend internal] load .dockerignore 0.0s => => transferring context: 299B 0.0s => CANCELED [backend builder 1/14] FROM docker.io/library/rust:1.75-slim-bullseye@sha256:598cba4e570656789d54c7776356af65b526 0.1s => => resolve docker.io/library/rust:1.75-slim-bullseye@sha256:598cba4e570656789d54c7776356af65b526261f64be8e0436b735d3d3bb156 0.0s => => sha256:598cba4e570656789d54c7776356af65b526261f64be8e0436b735d3d3bb156b 6.00kB / 6.00kB 0.0s => => sha256:466bd7fb2bc6b8aa9c36654421b6d560b1a5f04e47f51834eebc369bb24e3eec 1.31kB / 1.31kB 0.0s => => sha256:e1ddd21c4dc11ee6f5423c49851a9e67505df86e0cdb38c381dbf0736585cdaf 2.67kB / 2.67kB 0.0s => CANCELED [backend stage-1 1/7] FROM docker.io/library/debian:bullseye-slim@sha256:b257e5e831aa9949737638f6d323cd563347b2a55 0.2s => => resolve docker.io/library/debian:bullseye-slim@sha256:b257e5e831aa9949737638f6d323cd563347b2a5571d98b9b15eef0c7cd80b68 0.0s => => sha256:b257e5e831aa9949737638f6d323cd563347b2a5571d98b9b15eef0c7cd80b68 1.85kB / 1.85kB 0.0s => => sha256:482aabdceb859cc9ddc2e36867ac1ff6d3477bffcd05cac015bfc442c334aff4 529B / 529B 0.0s => => sha256:1dcedcb363a3e8070f3a0438cab8174b07fd23da25f04928c5111ccf7d856465 1.46kB / 1.46kB 0.0s => [backend internal] load build context 0.1s => => transferring context: 44.37kB 0.0s => CACHED [backend builder 2/14] RUN apt-get update && apt-get install -y pkg-config libssl-dev curl && curl 0.0s => CACHED [backend builder 3/14] WORKDIR /usr/src/app 0.0s => ERROR [backend builder 4/14] COPY backend/Cargo.toml backend/Cargo.lock ./backend/ 0.0s ------ > [backend builder 4/14] COPY backend/Cargo.toml backend/Cargo.lock ./backend/: ------ failed to solve: failed to compute cache key: failed to calculate checksum of ref aec1e5ba-82f3-4a53-b646-761684e639eb::ly5ucmdnwz1crv0y2vnvokqbm: "/backend/Cargo.lock": not found`` ``` This is because in `backend` the file `Cargo.lock` is missing, so as a workaround you have to run a build of the backend project first, while I think it is more correct that the file is included in the repository