Request for PHP Official to Provide Standalone Linux Binary Packages

[eatmeatball]

Description

Background

When embarking on the journey of software development, especially for newcomers, setting up a development environment can often be a complex and time-consuming process. Many developers may feel overwhelmed by environment configuration issues, which can hinder their learning experience. To reduce this barrier, several programming languages and frameworks have begun to offer standalone binary packages that are ready to use, rather than just source code.

Binary Packages vs Source Code

For beginners, one of the most significant challenges is figuring out how to build an entire development environment from scratch. In contrast, binary packages provide numerous advantages:

• Simplicity: Users only need to download and extract the package, without having to engage in complex compilation steps.
• Consistency: Different users or deployment environments can utilize the same version of PHP, minimizing issues related to version discrepancies.
• Time-saving: Newcomers can get up and running more quickly, allowing them to focus on learning PHP itself rather than on configuring it to run on their machines.
• For example, languages like Python and Node.js offer straightforward binary installation options. Users simply download the appropriate version and extract it, making it easy to use in any compatible environment. This significantly lowers the barrier to entry, enabling more people to quickly dive into programming.

Benefits of a Unified Ecosystem

Providing a consistent binary package also helps to create a more unified ecosystem. Here are several potential benefits:

• Reduced Fragmentation: When everyone uses the same binary version, community communication and troubleshooting become more efficient.
• User-friendly: New users can start with simple steps, without needing to delve into various compilation options and dependencies.
• Enhanced Community Support: A unified version means that the community can provide support and documentation more efficiently, reducing confusion caused by version differences.

Conclusion

We hope that the PHP official team will consider releasing a standalone Linux binary package for PHP. This initiative would greatly facilitate the learning and usage of PHP for newcomers, while also enhancing the uniformity and user experience across the PHP ecosystem. By drawing on the successful practices of other programming languages, we believe this change could attract more new users and increase engagement within the PHP community.

---

e1 node:

e1 golang

[iluuu1994]

There have been some plans to improve installation instructions. /cc @pronskiy @derickr

[ooing]

I think this is really necessary

[NattyNarwhal]

Miss me with the ChatGPT intro, but I think historically why this didn't happen:

• PHP is almost always used with your web server, be it loaded as a module or with (Fast)CGI via i.e. FPM. This wouldn't be a plug and play process by just extracting a tarball (i.e. you'd need to link with your build of Apache for mod_php, you'd need to set up the service and get the web server talking to it for i.e. FPM); the distribution packages build and install integration here.
• There has been semi-official packages already, be it Zend's commercial distribution or Ondrej and Remi's repositories (usually based and majorly enhanced from distribution packaging). Perhaps PHP as a project could do a better job of promoting or blessing these, but it risks accusations of favouritism.
  • That said, a lot of distros also tend to have their own support lifecycles separate from PHP's (i.e. Zend's LTS, Debian/EL/etc backporting fixes), it's sometihng to keep in mind. In theory, users are also supposed to talk with their dowstream first with issues (it's more obvious if you're paying them), but in practice everyone circumvents distro bug trackers and go directly to upstream.
• For people interested in consistency, they're probably already using containers. Most I tend to see (though I don't usually work with containerized Linux environments) tend to be distro PHP on i.e. Ubuntu or Alpine base images.

(Disclaimer for transparency: I provide a commercially supported PHP distribution for IBM i, and thus have worked on i.e. system integration stuff.)

[mouyong]

When I completed projects using PHP, it was tedious and complicated to deal with the environment independently for each deployment.

In different teams, the environmental dependencies of PHP are also different. When the team first switches to a unified environment, someone needs to complete the containerization process, which is also a complicated matter.

PHP currently cannot have an environment through one installation like nodejs, python, etc. Users are always required to build more additional adaptation environments (such as web servers nginx, apache).

When I want to migrate a PHP project from a monolithic project to a containerized project, the level of tedium is even higher. You need to select the Ubuntu system environment, choose the dependencies to install, and process how web requests are processed by the PHP interpreter. These are disaster-level difficulties for those with less overall experience. Basically, it is more difficult for users with 1 to 3 years of experience to complete it. But compared with python and nodejs, it is indeed very easy. Just need from the official image. Install the project dependencies and run the project to complete. Not PHP.

[JaguarJack]

When I write beginner tutorials, I find it relatively difficult from my personal perspective. I need to explain a lot, such as where to install PHP, where the PHP directory is, and how to configure PHP's environment variables to use the PHP interpreter in the console. Especially on Windows, if I don't use some integrated software, I really don't want to explain it to beginners; it's too troublesome.

In my vision, if the official PHP development team could take some time to make PHP an executable file and integrate the Composer package manager, it would be invaluable for the development of PHP. I see many RFC proposals that do not contribute to the popularization of PHP. What PHP needs is to lower the entry barrier for newcomers. I see other languages evolving, with their usage thresholds getting lower and lower, while PHP remains stagnant. Installing PHP on a new machine has been the same for the past ten years. This can be considered a regression.

Please give this issue the attention it deserves. I truly hope PHP will continue to improve and become more accessible.

[weijer]

This is really necessary 🎉

[AuroraYolo]

good idea

[woshijxh]

good idea

[wdwlrz]

we need it, just for a simple way of install and some simple scenes

[KingBes]

I think either make a PHP compiler

[kanyxmo]

This is really necessary 🎉

[iluuu1994]

Ok guys, please use the +1 button instead of spamming hundreds of people. :slightly_smiling_face:

[tlxf]

I strongly agree with this proposal, it is really necessary, and I hope PHP officials will consider it.

[echoyl]

+1

[jingjingxyk]

Standalone PHP Binary Packages

https://github.com/swoole/swoole-cli/releases

https://github.com/swoole/build-static-php/releases

usage ：

curl -fSL https://github.com/swoole/swoole-cli/blob/build_native_php/setup-php-cli-runtime.sh?raw=true | bash

curl -fSL  https://github.com/swoole/build-static-php/blob/main/setup-php-fpm-runtime.sh?raw=true | bash 

curl -fSL https://github.com/swoole/swoole-cli/blob/main/setup-swoole-cli-runtime.sh?raw=true | bash

[cmb69]

Especially on Windows, if I don't use some integrated software, I really don't want to explain it to beginners; it's too troublesome.

But exactly for Windows we are shipping binaries. I still do not understand what this feature request is about.

[NattyNarwhal]

I think you have to set up i.e. web servers and databases. Latter is expected with other languages (unless you’re using SQLite), but the former is a bit unusual other than getting a production web server to front for your app server, since your web application in i.e. Node or Python is an app server of its own.

That said, on Windows, XAMPP seems to be really popular for teaching, since it handles the setup of all of a historically popular AMP environment for you. When I was in school, they were using that; I have to imagine it’s popular elsewhere.

[iluuu1994]

but the former is a bit unusual other than getting a production web server to front for your app server

Well, there's php -S now, which works quite well most of the time.

I still do not understand what this feature request is about.

The description hints at two things:

1. Providing binaries
2. Improving installation instructions on the php.net website

While there's no interest for 1. from our side, 2. is already actively being discussed. We already provide binaries for Windows, macOS is covered by Brew, and Linux distros package PHP themselves. So instead, the installation page should give platform/distro specific instructions. We can definitely improve here.

As for building a universal binary that works for everybody: This is hard. People have different requirements. We would most likely need to bundle libraries statically, which means we'll be responsible for providing patches, picking the right versions (some people like stability, some bleeding-edge), etc.

That said, FrankenPHP does pretty much exactly that, in addition to bundling Caddy, a production ready webserver. Note though that it is a relatively new project, and not directly associated with the PHP group.