Huh this is a real paradigm shift! I'm eager to see how it is embraced by the community. Thanks Chris!

Wow, that's crazy... Thank you, Chris! Will try it soon!

I'm at a point where i think performance for 99.9% of apps and sites created is not that important considering the 20 monthly users and a crushed dev dream xD

This thing is absolutely INSANE. Awesome content, Chris!

Working with Go, I have become very accustomed to this convenient deployment method. I can't wait to do the same in PHP now ❤️ Thanks for the quick overview.

Really interesting, thanks for the overview. I'm excited to try this soon!

I've watched this video 4 times today, I love it!

Thank you for bringing me up to speed on this. Was wondering what it was!

Great episode as always!

Outside of the scope of the video for a second - @ 02:04 - I literally wet myself laughing. You've got a new subscriber... Onto the scope of the video. I have not PHP'd in over a decade because of Node and Go, except for the odd Laravel project that I would take over, and this certainly makes me want to check out PHP again because when I am not doing some fancy Kubernetes and Edge work, I use Caddy as my go to server because the API is stellar and you can set servers up on the fly with a couple API calls.

I think putting it architecturally side by side with nginx + fpm could provide clarity, thanks for sharing, cheers!

never had deployment issues for PHP. at least I learned some people struggle with this. Nice to know there is a complicated method that encapsulates the previously existing "complicated" method.

Awesome stuff, I'll check it out

great overview!

Frankenphp approach is very promising (and I ❤ 103 early hints). I would like to hear your thoughts about its mercure-based realtime module and laravel queues/jobs implementation using frankenphp Thank you for your Outstanding content! 🏆

I love the contained executable, it can be useful when making things for less technical people, you can't expect them to install docker or PHP on metal

I can't decide if I love this or really love this.

just found out about it and looks promising 👍

It's worth noting that your connection is still private regardless of the warning from the browser. The reason the browser complains is because it can't resolve the root CA for which signed the certificate since its self signed locally.

I love this! Gonna follow this expecting the Octane support

This is going to make life so much easier 😄

This looks insane… if you have any sort of app that is moderately complex we should test the $&@T out of it and see if it’s faster, concurrent requests and page loads on dinámica content etc etc… would love to see a deep dive on server deployment

Your last chapter reminded me of people, and perhaps me the most, spending hours upon winning two milliseconds in context of nginx vs caddy, when a relationship query is taking 500ms 🤣🤣

Interesting. Like to see what the cybersecurity guys make of it before I'd use in production.

I'am eager to test the build mode, and then run the packaged app binary in a distroless container as a production environment. Going to be fun to figure out how to run other processes like cronjob triggered artisan commanda in the same container or packaged app.

6:08 - I don’t copy .env files at all into docker images. At minimum probably best to inject into actual environment variables and reference somehow via getenv() (that’s just low level, your particular framework may vary), especially if they contain any secrets. This just avoids them sitting around in container images. In deployed environments, those env vars are injected via some other means (e.g. in Kubernetes via secrets or via secret manager in GCP, etc). In your local dev or insecure test environments, you can easily stub out those env vars via env_file in docker-compose for example.

7:53 - Great use case for multi-stage builds 😅 Sorry for all the comments,but I was wondering about that when I saw that this resulted in a binary. Like… whole app in a single binary? Sick. Very “go” too, lol. But yeah, do your build in one image, then in the next stage (image) you copy that over from the previous stage and you get a WAY smaller resulting image out of that single Dockerfile.

I'd be curious to learn what steps are required to secure a web server when you're running the standalone executable. Any different than a typical PHP deployment?

Crazy. I was just about to use Nginx Unit with PHP inside one container and now I see this.

how does it compare with preloading, JIT...etc ?

2:03 no problem buddy

“Worker mode” reminds me _a lot_ of OpenSwoole. This feels potentially more stable and easier to implement though. Wonder how they’d benchmark against each other.

Really awesome stuff... Btw few questions: 1. Does env still work? 2. How file storage works in this binary state, can it read storage files? 3. Blade view compiled files, where will they be stored?

How does it handle things like the storage directory? Should you just assume that you'll need to plug it into an s3 driver?

I think a fairly typical use case is to have nginx in front of various web applications/vhosts. Does frankenphp have any support for this, or just for a single application?

Wow

11:36 - re: Are you referring to the good ole’ Nginx + PHP-FPM combination?

I am used to deploy my built images and use these as multi purpose containers for the Scheduler and or Queue. Does this also work here?

How would the Laravel task scheduler be setup ? Will it leverage the existing binary or will you need to install PHP on the host machine and setup a cronjob?

Can we see some benchmark tests on a real world application please? Is it really a 3.5x boost? And what about requests per second?

What about logging and other stuff when you build the binary ?

Hi. I'm trying to run the frankphp in a different port. Is it possible to specify a port different from default (80) on run it? Thanks

i wanted to ship a mysql server as well , does it bundle that as well?

How would things like interacting with the filesystem work here?

Sounds interesting. My main question is, if you're already using Docker to package your app, what's the benefit of packaging it into a binary? Your docker image is still going to be prepackaged and ready to run, even if you've just built it traditionally using php-fpm and a dockerfile that installs composer prerequisites etc. If you are already packaging your app in a container for deployment, what would be the advantage of switching to this?

how do u deal with pecl extensions? that are not listed in the bash file ?

Is this recommended for production? It sounds like FrankenPHP does not support *Virtual Hosts* on a shared host. Another apparent downside, is if your Laravel app has additional services, such as email or cron jobs or queues. Does one maintain a database outside the docker image?

how easy is this to use with ssl? manual and automatic systems like letsencrypt?

How the process / the php app is kept alive or restart if chashes? Thanks

Mhhh… but what I’m not fully getting is, .. what if I have already a reverse proxy running? Eg Traefik or Caddy. Would I have then two reverse proxies?

Franken php to bundle backend, and deno (hopefully bun too) to bundle and deploy frontend. Maybe someone can come up with installer script for windows, shipping products is going to be smooth as f in future.

Is it best than swoole ?

It's quite beautiful and stunning. Though, the process itself is tedious and error-prone.

That middle finger 😲😲🫨

But I mean. Docker already is something you use to be able to deploy things in an easier way. If I have a dockerized application I can deploy it to any cloud environment like aws, azure etc with docker integration. I don't see the point

I remember yhe good old times when it was considered bloated if the executable exceeded a few megabytes in size :) oh how the turntables have been turning ;D

I don’t buy this. I move all complexity to my local machine, need to run docker, compile binary etc only to remove it from production server. Are we saving money on production servers? Whats the point? I understand it possible. I understand its new and cool but is it worth it?

so we are stopping to use apache or nginx that they are written with champion in performance languages such as C and C++ and we are using a server written in go? And do you name it as evolution?

Okay… so why not just use Go en leave PHP behind? All these steps vs go build.

omg Chris, I think you solved a problem that’s been blocking me for the past few months

When I am looking at any web stuff I can't believe that it is a binary code. It is super slow and absolutely religious by it's nature. While it is for the most part just an implementation of a prefab concept with a declarative language + some language that is targeting simple projects (getting problematic later). And overall everything web purposed is very similar to a game engine scope. I would expect true revolution for web with something like web-engine with specific IDE and editor. Game engine is an example of how you have an environment that is ready for all sorts of typical stuff and solutions for them in one place. And you don't have to remake everything if you just want to replace a physical engine or rendering pipeline. In few words: to have an actual architecture and not just bunch of unrelated stuff glued together hoping for the best. But I am quite delusional about web as I don't like browser and websites in the first place.

"you don't need to run docker"... whew, otherwise it would be DOA for me.

finally even PHP can suffer from a complex zero downtime deployment - thanks to single binaries.

Its like nodejs 😮

Great video, just wished there was less of those "I'm not sure" moments

I want to learn PHP, but there's so many other useful frameworks like Supabase, Appwrite and Pocketbase, I can't find a reason. Sorry.

this server is still amateur. Would like to use on a personal project but in real world I'd still choose apache or nginx

as long as {} and ; exist in PHP. I'm not going back.

like roadrunner. the f*king docker is terrible

2:03 no problem buddy