[QUESTION] deploying to production

[ezekel]

Hi

When deploying to production should we need to use Caddyfile or is this enough to deploy?

FROM dunglas/frankenphp:latest

ENV SERVER_NAME=mysite.com//just example

RUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"

RUN apt-get update && apt-get install -y \
    curl \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*


# Add additional PHP extensions here:
RUN install-php-extensions \
    pdo_mysql \
    gd \
    intl \
    zip \
    opcache

# Install Composer
RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer

COPY . /app

Thank you in advance

[withinboredom]

You can add @composer to your install-php-extensions list and have it install it. It also checks the SHA (IIRC) to ensure you have a non-corrupted composer installed.

Looks about right to me! Here's a real Dockerfile for a production service if you want to compare notes:

FROM dunglas/frankenphp:1-php8.3-bookworm AS builder

ARG EXTRA_EXTENSIONS="opcache"
RUN install-php-extensions @composer intl ctype mbstring apcu pdo pdo_pgsql zip $EXTRA_EXTENSIONS
RUN apt-get update && apt-get install -y inotify-tools && \
    rm -rf /var/lib/apt/lists/*

RUN cp "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"; \
    sed -i 's/variables_order = "GPCS"/variables_order = "EGPCS"/' "$PHP_INI_DIR/php.ini";

ENV SERVER_NAME=":8080" FRANKENPHP_CONFIG='worker /app/public/index.php'

RUN useradd -r -d /app -s /bin/bash -g root -G sudo -u 1000 caddy; \
    mkdir /data; \
    mkdir /config; \
    chown caddy:root -R /data; \
    chown caddy:root -R /config;

FROM builder AS production

COPY composer.json composer.lock /app/

RUN composer install --no-dev --optimize-autoloader --apcu-autoloader --no-scripts --no-plugins

COPY src /app/src
COPY public /app/public
COPY bin /app/bin

# run any plugins/scripts as needed
RUN COMPOSER_ALLOW_SUPERUSER=1 composer dump --optimize --apcu --no-dev

RUN echo "xdebug.mode=debug\nxdebug.discover_client_host=1\n" >> $PHP_INI_DIR/php.ini

USER 1000

FROM production AS tests

USER root

COPY . .
RUN composer install || composer install # silly workaround
RUN vendor/bin/pest

The docker-compose.yml file for development looks something like this:

x-service-build: &build
  context: .
  pull: true
  dockerfile: Dockerfile
  target: production
  args:
    EXTRA_EXTENSIONS: "xdebug"

x-service-env: &senv
  DATABASE_USER: root
  DATABASE_PASSWORD: insecure
  DATABASE_HOST: postgres
  DATABASE_PORT: '5432'
  DATABASE_NAME: postgres
  XDEBUG_SESSION: 1
  XDEBUG_CONFIG: "log_level=10"
  # comment out below to enable worker mode and disable xdebug stepping
  FRANKENPHP_CONFIG: ""

services:
  translation-init:
    image: funxtionatics/translation-system
    depends_on:
      postgres:
        condition: service_healthy
    build:
      <<: *build
    environment:
      <<: *senv
    restart: no
    volumes:
      - ./:/app
    command: ['/app/bin/init.sh']
  translation-tests:
    image: funxtionatics/translation-system
    depends_on:
      translation-init:
        condition: service_completed_successfully
    profiles:
      - tests
    build:
      <<: *build
    environment:
      <<: *senv
    volumes:
      - ./:/app
    command: ["vendor/bin/pest"]
  translation-service:
    image: funxtionatics/translation-system
    depends_on:
      translation-init:
        condition: service_completed_successfully
    build:
      <<: *build
    environment:
      <<: *senv
    volumes:
      - ./:/app
    command: ['/app/bin/watch.sh', 'frankenphp run -c /etc/caddy/Caddyfile']
    ports:
      - "8881:8080"
    stop_signal: SIGINT

And if you are curious, here's watch.sh

#!/usr/bin/env bash

sigint_handler()
{
  kill -9 $PID
  exit
}

trap sigint_handler SIGINT
trap sigint_handler SIGTERM

while true; do
  # commands to perform any work on changes
  composer dump -o --apcu
  bin/doctrine orm:schema-tool:update --force --complete

  $@ &
  PID=$!
  inotifywait -e modify -e move -e create -e delete -e attrib -r "$(pwd)/src" "$(pwd)/public" "$(pwd)/vendor"
  kill $PID
done

[ezekel]

@withinboredom

Thank you so much for this, this helps me a lot

[ezekel]

@withinboredom

Can I see your Caddyfile and what it looks like also I did not see in your Dockerfile that you copied the Caddyfile to the docker?
Is the app is laravel ? if that is Laravel why is no supervisor installed in the dockerfile?

[withinboredom]

It's using the default Caddyfile. We use multiple containers instead of a supervisor.

[ezekel]

@withinboredom

Is your app is Laravel?.

because you have this folders

COPY src /app/src
COPY public /app/public
COPY bin /app/bin

Thank you in advance

[withinboredom]

No, this app uses a mix of Symfony and Larvel.

[ezekel]

@withinboredom

I tried to follow some of your dockerfile and using multi stage, after I build I get 917.1MB is this correct ? I'm expecting I can get 1mb or something. my laravel app is only using API and default code for the API. no other than that.

FROM dunglas/frankenphp:1.1-php8.3-bookworm as builder


RUN install-php-extensions @composer intl gd pcntl ctype mbstring  pdo pdo_mysql zip

RUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"

RUN apt-get update && apt-get install -y \
    curl \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*

COPY . /app


FROM builder AS production

ENV SERVER_NAME=mysite.com

COPY composer.json  /app/

RUN composer install  --optimize-autoloader --apcu-autoloader --no-scripts --no-plugins

COPY public /app/public


ENTRYPOINT ["php", "artisan", "octane:frankenphp"]

Thank you in advance.

[withinboredom]

Mine is 205mb.

If your size is unexpectedly large:

• Do you have assets like videos or images?
• Do you need to add .git to your .dockerignore (unless you need the git history as part of your build)?

There's nothing wrong with a large image unless you need exceptionally short startup times (most people don't; a 1gb container starting up will still be faster -- and cheaper -- than a full-blown vm/machine) or you have to pay for the storage and need to cut costs.

[ezekel]

Hi @withinboredom

I'm getting 799.86mb, but my code is only API which the default during installation, no video and no images.

I also added dockerignore.

.dockerignore

.git/
vendor/
node_modules/
public/js/
public/css/
yarn-error.log
mysql-data/

This is my dockerfile the whole code.

RUN install-php-extensions \
    pdo_mysql \
    gd \
    intl \
    zip \
    opcache\
    pcntl \
    @composer

RUN apt-get update && apt-get install -y \
    curl \
    supervisor \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*


COPY . /app


FROM builder  AS development

RUN composer install

ENTRYPOINT ["php", "artisan", "octane:frankenphp"]

FROM builder  AS prod_build

RUN composer install \
    --ignore-platform-reqs \
    --no-interaction \
    --no-plugins \
    --no-scripts \
    --prefer-dist

RUN mv "$PHP_INI_DIR/php.ini-production" "$PHP_INI_DIR/php.ini"


FROM prod_build  AS production

COPY --from=prod_build /app/vendor/ /app

ENTRYPOINT ["php", "artisan", "octane:frankenphp"]

docker-compose

  php:
    container_name: frankencondobreeze
    build:
        context: .
        dockerfile: ./docker/web.dockerfile
        target: production
    image: frankenbreeze

Thank you in advance

[withinboredom]

Ah, are you building some node stuff there? Then that sounds like a normal size - ish.

I'd use a layer inspection tool to find out which layer is so big and which files/folders are responsible. Then, determine if you need them. For example, I have an app that has a big node_modules folder to build a frontend, but once the frontend is built, I don't need the node_modules folder. So, after I build the frontend in its own FROM, I copy the results into the final image.

If you have Docker Desktop, there are some free extensions for exploring layers.

[ezekel]

No, I don't use node and no frontend, I just put the node_modules in dockerignore. I will try the layer inspection. Yes I am using Docker Desktop Windows. thank you so much. I will be back.