feat(ci)🐳: Add Docker image build step to deployment workflow

- Introduced a new job in the GitHub Actions workflow to build a Docker image.
- Updated the Dockerfile to use a new base image and streamlined the build process.

Author: ericmjl

.github/workflows/deploy.yaml

@@ -51,6 +51,17 @@ jobs:
         with:
           source-dir: ./site
 
+  build-docker-image:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: prefix-dev/setup-pixi@v0.8.3
+        with:
+          pixi-version: v0.41.4
+          cache: true
+      - name: Build Docker image
+        run: |
+          docker build -t nams-docker .
 
   #     - name: Download environment tarball
   #       uses: actions/download-artifact@v3

scripts/Dockerfile

@@ -1,32 +1,16 @@
-# For use with both Dokku and Binder
-FROM continuumio/miniconda3
+FROM ghcr.io/prefix-dev/pixi:0.40.0 AS build
 
+WORKDIR /app
+COPY pixi.lock /app/pixi.lock
+COPY pyproject.toml /app/pyproject.toml
+COPY nams /app/nams
 
-# We isolate the conda environment setup step
-# because it is time consuming and a bit of a RAM hog.
-ADD environment.yml /environment.yml
-RUN conda env create -f /environment.yml
-RUN rm /environment.yml
+RUN pixi install
 
-# We put the custom source installation steps here
-# and not in the `environment.yml` file
-# to prevent Docker from rebuilding the environment
-# each time the source and notebooks change (which they will).
-# This is extremely time consuming and expensive during the build.
-ADD nams /tmp/setup/nams
-ADD setup.py tmp/setup/setup.py
-WORKDIR /tmp/setup
-RUN python setup.py install
-RUN rm -rf /tmp/setup
-
-# Now we add the repository to the Docker container
-ADD . /nams
-WORKDIR /nams
-ENV PATH="/opt/conda/envs/nams/bin:${PATH}"
-RUN python -m ipykernel install --name nams
+RUN pixi run python -m ipykernel install --user --name nams
 
 # Build docs in the container in this step
-RUN mkdocs build
+RUN pixi run build-docs
 
 # Run Python web server to serve up static files
 EXPOSE 80