Update Dockerfile

Dockerfile

@@ -18,20 +18,26 @@ FROM node:24-bookworm-slim AS webapp
 # which cannot read this repo's lockfile. 11.21.0 is the version declared in
 # devEngines and verified against pnpm-lock.yaml.
 RUN corepack enable && corepack prepare pnpm@11.21.0 --activate
+RUN apt-get update && apt-get install -y --no-install-recommends git && rm -rf /var/lib/apt/lists/*
+
 WORKDIR /build
 
-# Copy the whole repo (needed by the Expo/webpack build)
-COPY . .
+# The Space's build context may contain only this Dockerfile (HF uploads can
+# exclude the repo), so clone the source from GitHub instead of COPY . .
+# Pin to a commit SHA for reproducible builds. When you push new commits and
+# want them live, update SOURCE_REF (or override it as a Space build arg).
+ARG SOURCE_REPO=https://github.com/CloudCompile/social-app.git
+ARG SOURCE_REF=a89f05821ad42b3b88ccba1290d8ce7632b5a42a
+# Fetch by SHA (clone --branch only accepts refs). GitHub allows fetching
+# reachable commit SHAs directly.
+RUN git init . \
+ && git remote add origin ${SOURCE_REPO} \
+ && git fetch --depth 1 origin ${SOURCE_REF} \
+ && git checkout FETCH_HEAD
 
 # Install deps. package.json's postinstall runs lexicons:generate and
-# intl:compile, which the webpack build needs. If the build context lost the
-# lockfile (some Space uploads exclude it), fall back to a plain install.
-RUN if [ -f pnpm-lock.yaml ]; then \
-      pnpm install --frozen-lockfile || pnpm install --no-frozen-lockfile; \
-    else \
-      echo "[build] pnpm-lock.yaml missing from build context - regenerating" && \
-      pnpm install --no-frozen-lockfile; \
-    fi
+# intl:compile, which the webpack build needs.
+RUN pnpm install --frozen-lockfile || pnpm install --no-frozen-lockfile
 
 # postinstall generated lexicons + i18n catalogs; verify they exist (the
 # intl:compile-if-needed guard is skipped outside CI, so compile explicitly
@@ -43,7 +49,7 @@ RUN test -d src/lexicons && echo "[build] lexicons OK" \
 # Build the static web app with this PDS baked in as the default service,
 # so sign-in/sign-up default to this server (users can still pick another).
 # On HF Spaces, set a Space variable PDS_HOSTNAME and rebuild so this matches.
-ARG PDS_HOSTNAME=hf.space
+ARG PDS_HOSTNAME=cloudunity-gemma-api1.hf.space
 ENV EXPO_PUBLIC_DEFAULT_SERVICE=https://${PDS_HOSTNAME}
 ENV EXPO_PUBLIC_BUNDLE_IDENTIFIER=rochester-pds
 ENV NODE_ENV=production
@@ -304,10 +310,7 @@ ENV PDS_EMAIL_FROM_ADDRESS=
 # Skip email confirmation flow entirely (no SMTP on HF)
 ENV PDS_EMAIL_DISABLE_CONFIRMATION_LINK=true
 
-# Public hostname. Set this to your Space's public URL (as a Space secret or
-# variable named PDS_HOSTNAME) so the PDS advertises the right endpoint:
-#   https://<owner>-<space>.hf.space
-# Users' handles will be <name>.<that hostname>.
+# Public hostname. Users' handles will be <name>.<that hostname>.
 ENV PDS_HOSTNAME=cloudunity-gemma-api1.hf.space
 
 EXPOSE 7860