Incorporate beachhead files from the previous mono-repo

Dockerfile

@@ -0,0 +1,88 @@
+# syntax=docker/dockerfile:1
+
+################################################################################
+# Create a stage for building the application.
+
+ARG RUST_VERSION=1.71.1
+ARG APP_NAME=timing-beachhead
+ARG PACKAGE_NAME=beachhead
+FROM rust:${RUST_VERSION}-slim-bullseye AS build
+ARG APP_NAME
+ARG PACKAGE_NAME
+WORKDIR /app
+
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends \
+    build-essential \
+    pkg-config \
+    libssl-dev \
+    && \
+    apt-get clean && \
+    rm -rf /var/lib/apt/lists/*
+
+# Build the application.
+# Leverage a cache mount to /usr/local/cargo/registry/
+# for downloaded dependencies and a cache mount to /app/target/ for 
+# compiled dependencies which will speed up subsequent builds.
+# Leverage a bind mount to the src directory to avoid having to copy the
+# source code into the container. Once built, copy the executable to an
+# output directory before the cache mounted /app/target is unmounted.
+RUN --mount=type=bind,source=src,target=src \
+    --mount=type=bind,source=obsidian-portal,target=obsidian-portal \
+    --mount=type=bind,source=toggl-portal,target=toggl-portal \
+    --mount=type=bind,source=lectures-portal,target=lectures-portal \
+    --mount=type=bind,source=Cargo.toml,target=Cargo.toml \
+    --mount=type=bind,source=Cargo.lock,target=Cargo.lock \
+    --mount=type=cache,target=/app/target/ \
+    --mount=type=cache,target=/usr/local/cargo/registry/ \
+    <<EOF
+set -e
+cargo build --locked --release --package $PACKAGE_NAME
+cp ./target/release/$APP_NAME /bin/server
+EOF
+
+################################################################################
+# Create a new stage for running the application that contains the minimal
+# runtime dependencies for the application. This often uses a different base
+# image from the build stage where the necessary files are copied from the build
+# stage.
+#
+# The example below uses the debian bullseye image as the foundation for running the app.
+# By specifying the "bullseye-slim" tag, it will also use whatever happens to be the
+# most recent version of that tag when you build your Dockerfile. If
+# reproducability is important, consider using a digest
+# (e.g., debian@sha256:ac707220fbd7b67fc19b112cee8170b41a9e97f703f588b2cdbbcdcecdd8af57).
+FROM debian:bullseye-slim AS final
+
+# Install curl for health check, clean up apt
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends ca-certificates curl && \
+    apt-get clean && \
+    rm -rf /var/lib/apt/lists/*
+
+# Disabled to allow read access to the database file.
+## Create a non-privileged user that the app will run under.
+## See https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#user
+#ARG UID=10001
+#RUN adduser \
+#    --disabled-password \
+#    --gecos "" \
+#    --home "/nonexistent" \
+#    --shell "/sbin/nologin" \
+#    --no-create-home \
+#    --uid "${UID}" \
+#    appuser
+#USER appuser
+
+# Copy the executable from the "build" stage.
+COPY --from=build /bin/server /bin/
+
+# Expose the port that the application listens on.
+ENV ADDRESS=0.0.0.0:3000
+EXPOSE 3000
+
+HEALTHCHECK \
+  CMD curl -f http://localhost:3000/health || exit 1
+
+# What the container should run when it is started.
+CMD ["/bin/server"]