Dockerfile

Rama main · réplica de lectura del repositorio original.

FROM composer:2 AS composer_bin

FROM php:8.2-apache

COPY --from=composer_bin /usr/bin/composer /usr/bin/composer

RUN apt-get update && apt-get install -y \
    libsqlite3-dev \
    libzip-dev \
    libpng-dev \
    libfreetype6-dev \
    libjpeg62-turbo-dev \
    && docker-php-ext-configure gd --with-freetype --with-jpeg \
    && docker-php-ext-install pdo pdo_sqlite zip gd \
    && apt-get clean && rm -rf /var/lib/apt/lists/*

RUN a2enmod rewrite

# The base image's default vhost inherits AllowOverride None for /var/www/,
# which makes it silently ignore .htaccess (the rewrite-everything-to-
# index.php rule never applies) and can leave requests hitting Apache's
# stricter default access rules -- a common cause of an immediate 403 on a
# fresh php:8.2-apache container. Grant this app's directory its own
# explicit, permissive config instead of depending on the base image's
# inherited defaults.
RUN { \
    echo '<Directory /var/www/html/>'; \
    echo '    Options FollowSymLinks'; \
    echo '    AllowOverride All'; \
    echo '    Require all granted'; \
    echo '</Directory>'; \
    } > /etc/apache2/conf-available/paragrafy.conf \
    && a2enconf paragrafy

WORKDIR /var/www/html

# Build from the local checkout, not a fresh git clone -- cloning from GitHub
# at build time meant Docker's layer cache could silently keep serving an old
# commit even after `docker compose up -d --build` (nothing in the Dockerfile
# changes just because the remote repo did, so the RUN git clone layer never
# invalidates on its own). Copying the local context always picks up the
# code you actually have checked out. See .dockerignore for what's excluded
# (in particular: local data/, .git/, and any local .env files).
COPY . /var/www/html/

# TOTP (spomky-labs/otphp) + QR-code rendering (endroid/qr-code) dependencies.
# --no-dev/--optimize-autoloader keep the vendored footprint production-only;
# vendor/ itself isn't committed (see .gitignore), so this is the only place
# a Docker install actually gets it.
RUN composer install --no-dev --optimize-autoloader --no-interaction --working-dir=/var/www/html

# Persistent data (DB, config.php, backups, .env) lives OUTSIDE the web-served
# /var/www/html docroot -- a security-incident forensics review on 2026-09-07
# found that self-hosted setups which mount their data volume inside the
# docroot (as this project's own docker-compose.yaml did before this fix)
# leave DB/config/.env reachable over HTTP the moment any vhost/.htaccess
# protection in front of the container is missing or misconfigured. Placing
# it next to (not inside) the docroot means there's nothing to serve even in
# that failure case.
RUN mkdir -p /var/www/data \
    && chown -R www-data:www-data /var/www/html /var/www/data \
    && find /var/www/html -type d -exec chmod 755 {} + \
    && find /var/www/html -type f -exec chmod 644 {} + \
    && chmod +x /var/www/html/docker-entrypoint.sh \
    && chmod 750 /var/www/data

ENV PARAGRAFY_DATA_DIR=/var/www/data

ENTRYPOINT ["/var/www/html/docker-entrypoint.sh"]
CMD ["apache2-foreground"]