From 29c6e6afd1f5256e69f9244b4e50515265f92b4a Mon Sep 17 00:00:00 2001
From: lobbystack <236289573+lobbystack@users.noreply.github.com>
Date: Tue, 29 Sep 2026 14:01:33 -0400
Subject: [PATCH] Drop BuildKit cache mounts so Railway accepts the server
 Dockerfile

Railway rejects cache mounts without an id prefixed by its service ID,
so every sync server deploy since mid-September failed before building.
The mounts only cached one cargo install.
---
 apps/server/Dockerfile | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/apps/server/Dockerfile b/apps/server/Dockerfile
index c705bb1..37a449a 100644
--- a/apps/server/Dockerfile
+++ b/apps/server/Dockerfile
@@ -6,9 +6,9 @@ RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates
 	&& rm -rf /var/lib/apt/lists/* \
 	&& curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --default-toolchain 1.91 --profile minimal \
 	&& rustup target add wasm32-unknown-unknown
-RUN --mount=type=cache,target=/root/.cargo/registry \
-	--mount=type=cache,target=/root/.cargo/git \
-	cargo install wasm-bindgen-cli --version 0.2.127 --locked
+# No BuildKit cache mounts: Railway rejects them unless their id names the
+# Railway service, which would tie this file to one deployment.
+RUN cargo install wasm-bindgen-cli --version 0.2.127 --locked
 COPY . .
 RUN bun install --frozen-lockfile
 RUN bun run --filter @noura/server build:release