https://frankenphp.dev/ seems to be a good PHP engine (alternative) that is said to be faster and requires lessm configuration.
It also seems to be included in Caddy a webserver in Go, which I can recommend as automates much stuff away (like HTTPS certificates) in a reliable way.
With FrankenPHP, Caddy acts as a PHP application server that delivers PHP pages about 4x faster than Swoole or RoadRunner: no need for php-fpm (FastCGI).
You could’ve answered that question with a few minutes of google/web engine of your choice.
My thoughts about it: whatever you might gain in performance from using caddy+frankenphp you will probably loose more when it comes to maintenance and support.
Interesting for folks who are at least advanced in that field and won’t need much support, but for most users easier support just wins…
Also, as for the nextcloud thread I have already linked it in the op, I was asking for more experience here. Also such a thread drastically improves seo/search ability and can be used for further experience sharing, just so people don’t end up accidentally finding blog posts of people setting up a usual php nextcloud installation, y’know?
In a few posts you might summarize what you actually want to know and what you’re trying to do.
Because the first questions you pose in the title and post are purely rhetorical and as such a waste of people’s time.
The blog post was specifically referred by the creator in a thread in the caddy community (the thread is not worth looking at, the OP is basically baiting for a howto without giving anywhere near enough information).
Not sure what you consider as “usual php nextcloud installation”, but afaik caddy is not the “usual” webserver.
So this blogpost is already showing a good part of the way, and we know that caddy works well with frankenphp so it’s safe to assume that the smaller part is easier (like… not installing/uninstalling php-fpm and instead going with the docs from frankenphp?)
If you’re actually trying to collect and organize knowledge, then go and state that in the title. Because someone looking for a collection or guide is certainly not gonna expect it unter this title - so much for searchability.
But this is as much as I can and will contribute here…
I get the impression that FrankenPHP, at least for now, is aimed more at developers and/or dev ops who want to deploy their applications as some kind of appliance, preferably as containers, and/or on some kind of infrastructure as code platform. So I think it might also be interesting for projects like the Nextcloud Community Docker Images or Nextcloud AIO, as it might simplify image creation and maintenance.
Of course, that doesn’t mean you can’t use it for a “manual” installation directly on the OS, they even provide binaries, but their documentation is definitely lacking in detail and assumes you already know how Caddy works, which is what it’s built on. It also abstracts away a lot of the knobs you can turn on a standard LAMP stack, which I personally am not necessarily a fan of.
I’ve had my instance running for a little bit now, and the only issues I’m encountering are
The OwnCloud Console doesn’t seem to work when invoked via the CLI, but the OCC app works perfectly.
All others are related to a low-spec server.
Also it may be worth noting that while my post does mention FrankenPHP, it doesn’t do so in a very obvious way, so it’s possible to overlook on Google. Please let people ask questions - that’s what a forum is for.
- JCake
