tfw you have more ephemeral storage than upstream bandwidth

``` FROM python:3.10-slim AS base

RUN apt update && apt -y install zstd

ENV DATASETTE_SECRET 'sosecret' RUN --mount=type=cache,target=/root/.cache/pip pip install -U datasette datasette-pretty-json datasette-graphql

ENV PORT 8080 EXPOSE 8080

FROM base AS pack

COPY . /app WORKDIR /app

RUN datasette inspect --inspect-file inspect-data.json RUN zstd --rm *.db

FROM base AS unpack

COPY --from=pack /app /app WORKDIR /app

CMD ["/bin/bash", "-c", "shopt -s nullglob && zstd --rm -d .db.zst && datasette serve --host 0.0.0.0 --cors --inspect-file inspect-data.json --metadata metadata.json --create --port $PORT .db"] ```

I noticed the image was large when using fly. Is it possible to use a -slim base?

On second thought any kind of quick-to-decompress-on-startup could be helpful if we're paying for the container registry and deployment bandwidth but not ephemeral storage.

On fly.io. This particular database goes from 1.4GB to 200M. Slower, part of that might be having no --inspect-file?

``` $ datasette publish fly ... --generate-dir /tmp/deploy-this ... $ mksquashfs large.db large.squashfs $ rm large.db # don't accidentally put it in the image $ cat Dockerfile FROM python:3.8 COPY . /app WORKDIR /app

ENV DATASETTE_SECRET 'xyzzy' RUN pip install -U datasette

RUN datasette inspect large.db --inspect-file inspect-data.json

ENV PORT 8080 EXPOSE 8080 CMD mount -o loop -t squashfs large.squashfs /mnt; datasette serve --host 0.0.0.0 -i /mnt/large.db --cors --port $PORT ```

It would also be possible to copy the file onto the ~6GB available on the ephemeral container filesystem on startup. A little against the spirit of the thing? On this example the whole docker image is 2.42 GB and the squashfs version is 1.14 GB.