wes/digital_garden
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clean up/fixed comments in dockerfile

Browse Source
This commit is contained in:
wes
2025-05-29 12:37:11 -04:00
parent 0563f646b2
commit 41078e7885
1 changed files with 3 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Dockerfile
+3 -24
View File
@@ -8,15 +8,12 @@ USER node
WORKDIR /home/node/app WORKDIR /home/node/app
# Copy the locally cloned Quartz source code from the build context # Copy the locally cloned Quartz source code from the build context
# This 'quartz_framework_source' dir is expected to be in the build context root, # This 'quartz' dir is expected to be in the build context root,
# prepared by the update_quartz_docker.sh script. # prepared by the update_quartz_docker.sh script.
COPY --chown=node:node quartz/ . COPY --chown=node:node quartz/ .
# Now /home/node/app contains the full cloned Quartz repo structure,
# including its package.json, its quartz/ directory with bootstrap-cli.mjs, etc.
# Install dependencies based on the cloned Quartz source's package.json # Install dependencies based on the cloned Quartz source's package.json
RUN npm ci RUN npm ci
# This will also make ./node_modules/.bin/quartz available, pointing to ./quartz/bootstrap-cli.mjs
# Now, copy your specific custom configuration files and the prepared content # Now, copy your specific custom configuration files and the prepared content
# from the root of your deployment repo (the build context's root) # from the root of your deployment repo (the build context's root)
@@ -24,6 +21,7 @@ RUN npm ci
# from the cloned Quartz source if they share the same names/paths. # from the cloned Quartz source if they share the same names/paths.
COPY --chown=node:node quartz.config.ts ./quartz.config.ts COPY --chown=node:node quartz.config.ts ./quartz.config.ts
COPY --chown=node:node quartz.layout.ts ./quartz.layout.ts COPY --chown=node:node quartz.layout.ts ./quartz.layout.ts
# If you have other custom files/dirs at the root of your deployment repo that Quartz needs: # If you have other custom files/dirs at the root of your deployment repo that Quartz needs:
# e.g., custom assets not part of Obsidian content, or custom components to overlay # e.g., custom assets not part of Obsidian content, or custom components to overlay
# COPY --chown=node:node assets/ ./assets/ # COPY --chown=node:node assets/ ./assets/
@@ -32,29 +30,10 @@ COPY --chown=node:node quartz.layout.ts ./quartz.layout.ts
# Copy the Obsidian content prepared by the host script into ./content # Copy the Obsidian content prepared by the host script into ./content
COPY --chown=node:node content/ ./content/ COPY --chown=node:node content/ ./content/
# Now run the build command. # Build the Quartz site
# `npx quartz build` should work because:
# 1. `npm ci` (based on the framework's package.json) made node_modules/.bin/quartz available,
# pointing to the local ./quartz/bootstrap-cli.mjs.
# 2. It will use your custom quartz.config.ts, quartz.layout.ts, and ./content.
RUN npx quartz build RUN npx quartz build
# Output is expected in /home/node/app/public # Output is expected in /home/node/app/public
# ---- START DEBUG (Optional) ----
# USER root # If you need root to ls everything for debug
# RUN echo "Listing contents of /home/node/app after all copies:" && ls -lA /home/node/app
# RUN echo "Listing contents of /home/node/app/content:" && ls -lA /home/node/app/content
# RUN echo "Listing contents of /home/node/app/public after build:" && ls -lA /home/node/app/public
# RUN echo "Checking for /home/node/app/public/index.html:" && \
# if [ -f /home/node/app/public/index.html ]; then \
# echo "index.html found. First few lines:"; \
# head -n 10 /home/node/app/public/index.html; \
# else \
# echo "index.html NOT FOUND in /home/node/app/public!"; \
# fi
# USER node # Switch back if you changed it
# ---- END DEBUG ----
# Stage 2: Serve the static files with NGINX # Stage 2: Serve the static files with NGINX
FROM nginx:alpine FROM nginx:alpine