h-m-m/Dockerfile

FROM php:cli

WORKDIR /app

RUN apt-get update \
  && apt-get install -y --no-install-recommends \
  libonig-dev xclip xsel wl-clipboard

RUN docker-php-ext-install mbstring

COPY ./h-m-m .

CMD ./h-m-m $file
Add Dockerfile 2022-09-15 19:01:21 +02:00			`FROM php:cli`

			`WORKDIR /app`

			`RUN apt-get update \`
			`&& apt-get install -y --no-install-recommends \`
			`libonig-dev xclip xsel wl-clipboard`

removed pcntl 2022-09-18 11:25:49 +02:00			`RUN docker-php-ext-install mbstring`
Add Dockerfile 2022-09-15 19:01:21 +02:00
Copy h-m-m to image as one of the final steps of the build Each edit to the h-m-m script was triggering a full image rebuild, including the slow apt-get and docker-php-ext-install steps. I figure that the h-m-m script itself is more likely to change than the system installs. Moving the COPY to after those operations means that each time h-m-m changes, the `docker build` can use the cache for the slow operations, and just add a new layer for the COPY at the end. Plus `chmod +x h-m-m` is unnecessary as h-m-m already has the executable bit set. 2022-09-29 11:03:40 +02:00			`COPY ./h-m-m .`
Add Dockerfile 2022-09-15 19:01:21 +02:00
Update Dockerfile Add a variable 2024-03-27 03:55:12 +01:00			`CMD ./h-m-m $file`