Who's using serversideup/php? Drop your link below!

[jaydrogers]

Hey all,

We're so grateful for this community and the continuous growth we're seeing together. Hitting 1.5 million Docker pulls has been amazing, but what's even better is meeting all the awesome people building with these images.

We'd love to hear what you're actually creating with serversideup/php - not just the stats, but the real projects!

Drop a link below if you're comfortable sharing:

• What are you building?
• How's your experience been?
• What's your deployment setup look like?

Looking forward to seeing what everyone's working on! ✌️

[luisdalmolin]

This is not officially released yet, but I've been building this package to deploy Laravel apps using SST, and it uses the Serverside Up Docker images: https://github.com/kirschbaum-development/sst-laravel

Also been using with some clients in their production applications. Mostly running it in AWS Fargate. The packages are amazing and give so much flexibility. With the FrankedPHP package coming, it will even be able to run Octane.

In this client we are working, we have a full Terraform set up where he configures and deploys multiple applications to ECS Fargate. We are waiting for the FrankenPHP image to be stable to enable Octane in some of their apps.

[jaydrogers]

Awesome! v4 is now released with FrankenPHP and Octane so build away 🤓 https://github.com/serversideup/docker-php/releases/tag/v4.0.0

[Jamesking56]

We're using your images for Varsuite Core website management platform: vs-core.com

We have deployed your images to our own Kubernetes cluster, the images are an absolute dream to use, thank you so much.

[jaydrogers]

Very cool! Thanks for the kind words and keep up the good work 👍

[kohenkatz]

At SaferMobility, we are working on switching from our own custom FrankenPHP-based images to your new v4 images for our university campus safety and bank employee safety platforms. It's been really great to switch from our cobbled-together scripts to something that does all the same things in a much more polished and dependable way. We currently deploy using Docker Compose on Ubuntu servers, but we are evaluating using Kubernetes on Talos Linux. (We also have a few open-source contributions of our own, and we're looking to increase those too.)

[jaydrogers]

Super cool! It's so wild to see the use cases of what serversideup/php is powering. Great product. We're extremely grateful for your contributions to the project too! 🙏

We currently deploy using Docker Compose on Ubuntu servers, but we are evaluating using Kubernetes on Talos Linux.

Interesting! Make the choice that's best for you, but I do have a relevant experience about self-hosting K8s if you're interested 🤓

I spent 500+ hours trying to learn how to self-host K8s to switch to Swarm 10 hours after that 🤪

If you're comfortable with Compose, the syntax for Swarm is almost the same. It's often an overlooked solution because many cloud companies don't make money off of it, but it's been a very feature mature solution and has worked great for our use cases.

K8s is great if you must exceed 99.999% uptime. But with the right configs with Swarm you can exceed that too. Swarm gives you the zero-downtime deployments and rolling updates that compose can't give you, but the syntax is almost the same.

We also have Spin which helps configure Ubuntu Swarm servers for you if needed and it's highly optimized to work with serverisdeup/php: https://serversideup.net/open-source/spin/

Not saying you need to use Swarm, but it should at least cross your radar because the simplicity is worth it if it checks your boxes 😃

[kohenkatz]

@jaydrogers Thanks for the suggestions, I will definitely look into them! Part of the reason we started looking at K8S was because we use GitLab and wanted to see if their "Auto Devops" features will help us, but we're not committed to it if there's something else that will be better for us.

[jaydrogers]

We run everything on a self-hosted GitLab instance too 🤓

I saw the Auto DevOps feature when I was looking into things, but honestly -- I don't feel like I am missing anything.

It was pretty straight forward to create a shared CI/CD template library and all our projects just call that for automated "push to deploy" pipelines. We love using GitLab! I can't believe everything you get in the open source version 🤯

[sawirricardo]

https://sawirly.com - shortener urls focusing on privacy first
https://golden-pots.com - ecommerce for electronic parts
https://dbtv.my.id - Church App
https://hob.my.id - ecommerce
https://realworld-laravel.sawirstudio.com
https://myvivaldy.com - Clinic Management System

My deployment TL;DR

1. Build Dockerfile
2. Push the image to my prod VPS using Unregistry
3. Profit

See more in detail in one of my Github Realworld Laravel for the deployment

ARG USER_ID=82
ARG GROUP_ID=82

FROM serversideup/php:8.4-fpm-nginx-alpine AS base

USER root

ARG USER_ID
ARG GROUP_ID

RUN install-php-extensions bcmath gd exif intl

RUN docker-php-serversideup-set-id www-data $USER_ID:$GROUP_ID && \
    docker-php-serversideup-set-file-permissions --owner $USER_ID:$GROUP_ID --service nginx

WORKDIR /var/www/html
COPY --chown=www-data:www-data composer.json composer.lock ./
RUN composer install --no-dev --no-interaction --no-plugins --no-scripts --prefer-dist

USER www-data

FROM node:24-alpine AS static-assets

WORKDIR /app
COPY package*.json vite.config.js ./
COPY --from=base --chown=www-data:www-data /var/www/html/vendor ./vendor
RUN npm ci
COPY . .
RUN npm run build


FROM serversideup/php:8.4-fpm-nginx-alpine

WORKDIR /var/www/html

USER root

ARG USER_ID
ARG GROUP_ID

RUN install-php-extensions bcmath gd exif intl

RUN docker-php-serversideup-set-id www-data $USER_ID:$GROUP_ID && \
    docker-php-serversideup-set-file-permissions --owner $USER_ID:$GROUP_ID --service nginx

# Install PostgreSQL repository and keys
RUN apk add --no-cache gnupg && \
    mkdir -p /usr/share/keyrings && \
    curl -fSsL https://www.postgresql.org/media/keys/ACCC4CF8.asc | gpg --dearmor > /usr/share/keyrings/postgresql.gpg

# Install system dependencies
RUN apk add --no-cache \
    postgresql17-client
# openssh-client \
# git \
# git-lfs \
# jq \
# lsof \
# vim

# Configure shell aliases
RUN echo "alias ll='ls -al'" >> /etc/profile && \
    echo "alias a='php artisan'" >> /etc/profile && \
    echo "alias logs='tail -f storage/logs/laravel.log'" >> /etc/profile

ENV PHP_OPCACHE_ENABLE=1
ENV SSL_MODE=mixed

COPY --from=base --chown=www-data:www-data /var/www/html/vendor ./vendor
COPY --from=static-assets --chown=www-data:www-data /app/public/build ./public/build

COPY --chown=www-data:www-data composer.json composer.lock ./
COPY --chown=www-data:www-data app ./app
COPY --chown=www-data:www-data bootstrap ./bootstrap
COPY --chown=www-data:www-data config ./config
COPY --chown=www-data:www-data database ./database
COPY --chown=www-data:www-data lang ./lang
COPY --chown=www-data:www-data public ./public
COPY --chown=www-data:www-data routes ./routes
COPY --chown=www-data:www-data storage ./storage
COPY --chown=www-data:www-data resources ./resources
COPY --chown=www-data:www-data artisan artisan

RUN composer dump-autoload

# RUN mkdir -p /etc/nginx/conf.d && \
#     chown -R www-data:www-data /etc/nginx && \
#     chmod -R 755 /etc/nginx

USER www-data

Then my docker-compose.yml

services:
  app:
    build:
      context: .
      dockerfile: Dockerfile
      args:
        USER_ID: 82
        GROUP_ID: 82
    image: sawirstudio/realworld-laravel:latest
    platform: linux/amd64

And many more! Thanks @jaydrogers !

[K2ouMais]

https://sawirly.com - shortener urls focusing on privacy first https://golden-pots.com - ecommerce for electronic parts https://dbtv.my.id - Church App https://hob.my.id - ecommerce https://realworld-laravel.sawirstudio.com https://myvivaldy.com - Clinic Management System

My deployment TL;DR

1. Build Dockerfile
2. Push the image to my prod VPS using Unregistry
3. Profit

See more in detail in one of my Github Realworld Laravel for the deployment

ARG USER_ID=82
ARG GROUP_ID=82

FROM serversideup/php:8.4-fpm-nginx-alpine AS base

USER root

ARG USER_ID
ARG GROUP_ID

RUN install-php-extensions bcmath gd exif intl

RUN docker-php-serversideup-set-id www-data $USER_ID:$GROUP_ID && \
    docker-php-serversideup-set-file-permissions --owner $USER_ID:$GROUP_ID --service nginx

WORKDIR /var/www/html
COPY --chown=www-data:www-data composer.json composer.lock ./
RUN composer install --no-dev --no-interaction --no-plugins --no-scripts --prefer-dist

USER www-data

FROM node:24-alpine AS static-assets

WORKDIR /app
COPY package*.json vite.config.js ./
COPY --from=base --chown=www-data:www-data /var/www/html/vendor ./vendor
RUN npm ci
COPY . .
RUN npm run build


FROM serversideup/php:8.4-fpm-nginx-alpine

WORKDIR /var/www/html

USER root

ARG USER_ID
ARG GROUP_ID

RUN install-php-extensions bcmath gd exif intl

RUN docker-php-serversideup-set-id www-data $USER_ID:$GROUP_ID && \
    docker-php-serversideup-set-file-permissions --owner $USER_ID:$GROUP_ID --service nginx

# Install PostgreSQL repository and keys
RUN apk add --no-cache gnupg && \
    mkdir -p /usr/share/keyrings && \
    curl -fSsL https://www.postgresql.org/media/keys/ACCC4CF8.asc | gpg --dearmor > /usr/share/keyrings/postgresql.gpg

# Install system dependencies
RUN apk add --no-cache \
    postgresql17-client
# openssh-client \
# git \
# git-lfs \
# jq \
# lsof \
# vim

# Configure shell aliases
RUN echo "alias ll='ls -al'" >> /etc/profile && \
    echo "alias a='php artisan'" >> /etc/profile && \
    echo "alias logs='tail -f storage/logs/laravel.log'" >> /etc/profile

ENV PHP_OPCACHE_ENABLE=1
ENV SSL_MODE=mixed

COPY --from=base --chown=www-data:www-data /var/www/html/vendor ./vendor
COPY --from=static-assets --chown=www-data:www-data /app/public/build ./public/build

COPY --chown=www-data:www-data composer.json composer.lock ./
COPY --chown=www-data:www-data app ./app
COPY --chown=www-data:www-data bootstrap ./bootstrap
COPY --chown=www-data:www-data config ./config
COPY --chown=www-data:www-data database ./database
COPY --chown=www-data:www-data lang ./lang
COPY --chown=www-data:www-data public ./public
COPY --chown=www-data:www-data routes ./routes
COPY --chown=www-data:www-data storage ./storage
COPY --chown=www-data:www-data resources ./resources
COPY --chown=www-data:www-data artisan artisan

RUN composer dump-autoload

# RUN mkdir -p /etc/nginx/conf.d && \
#     chown -R www-data:www-data /etc/nginx && \
#     chmod -R 755 /etc/nginx

USER www-data

Then my docker-compose.yml

services:
  app:
    build:
      context: .
      dockerfile: Dockerfile
      args:
        USER_ID: 82
        GROUP_ID: 82
    image: sawirstudio/realworld-laravel:latest
    platform: linux/amd64

And many more! Thanks @jaydrogers !

Can I ask you the reason for the installing on "base" the composer dependencies instead of installing it on the last stage?

[sawirricardo]

I took reference from coolify's

https://github.com/coollabsio/coolify/blob/v4.x/docker/production/Dockerfile

[K2ouMais]

The reason I am asking is because you could have saved one stage and a lot of COPY layers, that are beeing added for no reason into your Image, making those bigger, than it needs to be.

[sawirricardo]

you mean we can delete the base and directly use the last layer (+ the static-assets layer)?

[K2ouMais]

Yes you can get rid of the base stage.

You are only using it to install the composer packages and on the last stage you are copying everything back and with "COPY" adding a lot o layers into your image.

Try this:

#########################################
# Build NPM Assets
#########################################

FROM node:24-alpine AS static-assets

WORKDIR /app
COPY . .
RUN npm ci && \
    npm run build

#########################################
# Build base image / Install composer dependencies
#########################################

FROM serversideup/php:8.4-fpm-nginx-alpine AS base

WORKDIR /var/www/html

USER root

ARG USER_ID
ARG GROUP_ID

ENV PHP_OPCACHE_ENABLE=1
ENV SSL_MODE=mixed

# COPY the NPM built assets
COPY . .
COPY --from=static-assets --chown=www-data:www-data /app/public/build ./public/build

# Install apk packages and PostgreSQL client
RUN apk add --no-cache gnupg postgresql17-client && \
    mkdir -p /usr/share/keyrings && \
    curl -fSsL https://www.postgresql.org/media/keys/ACCC4CF8.asc | gpg --dearmor > /usr/share/keyrings/postgresql.gpg && \
    \
    # Install PHP Extensions \
    install-php-extensions bcmath gd exif intl && \
    \
    # Set id and file permissions \
    docker-php-serversideup-set-id www-data $USER_ID:$GROUP_ID && \
    docker-php-serversideup-set-file-permissions --owner $USER_ID:$GROUP_ID --service nginx && \
    \
    # Install Composer packages and dump autoload \
    composer install --no-dev --no-interaction --no-plugins --no-scripts --prefer-dist && \
    composer dump-autoload

USER www-data

Here you only have 1 COPY and 1 RUN to do everything you need. (2 Layers)

EDIT:
I had to edit, because if was something wrong and I had to add 1 more layer to the base stage.
Your image should be a bit smaller this way.

[adiologydev]

• Korrektly.com - AI-Search and RAG Platform (Private Beta, powering Coolify Docs atm)
• ColorBuk.com - Coloring Page Generator
• MarkdownAnything.com - Backend API (WIP)
• https://github.com/climactic/peeper - Open-Source Database Management Tool (WIP)

These are my main ones. But I've got enough domains to keep making projects :D

Experience with SSU PHP has been pretty good. I wish we had logging for s6-overlays in the main process instead of having to rely on log providers, but other than that, pretty good. The docs were a bit hazy to understand at first, but now I know all I need to know.

Deployment is either coolify -> docker-compose -> build -> deploy on every commit OR release -> build -> push to registry -> trigger coolify to pull and deploy (zero-downtime).

To make deploying with pre-built images easier, I've added some PRs to Coolify, which let you have custom entrypoints so that deploying horizon, inertia, scheduler, workers, etc. becomes easier and you no longer have to rely on s6-overlay if you're using pre-built images. Docker Compose is still a workaround at the moment if you want separate containers for each service.

To give context, I'm a volunteer at Coolify, and I am the founder of Climactic, which is a software studio :)
SSU PHP is one of the many reasons why I am confident in working with Laravel because I love self-hosting!

[jaydrogers]

Wow! You're a busy dude 🤯

Thanks for your helping out our brothers and sisters at Coolify. Self-hosting FTW 💪

Keep up the great work 👍