Php для windows установщик

PHP: Hypertext Preprocessor

This site is dedicated to supporting PHP on Microsoft Windows. It also supports ports of PHP extensions or features as well as providing special builds for the various Windows architectures. If you like to build your own PHP binaries, instructions can be found on the Wiki.

PECL For Windows

PECL extensions for Windows is being worked on. Windows DLL can be downloaded right from the PECL website.

The PECL extension release and snapshot build directories are browsable directly.

Which version do I choose?

IIS

Apache

Please use the Apache builds provided by Apache Lounge. They provide VC15 and VS16 builds of Apache for x86 and x64. We use their binaries to build the Apache SAPIs. With Apache, using the apache2handler SAPI, you have to use the Thread Safe (TS) versions of PHP.

VC15 & VS16

More recent versions of PHP are built with VC15 or VS16 (Visual Studio 2017 or 2019 compiler respectively) and include improvements in performance and stability. — The VC15 and VS16 builds require to have the Visual C++ Redistributable for Visual Studio 2015-2019 x64 or x86 installed

TS and NTS

TS refers to multithread capable builds. NTS refers to single thread only builds. Use case for TS binaries involves interaction with a multithreaded SAPI and PHP loaded as a module into a web server. For NTS binaries the widespread use case is interaction with a web server through the FastCGI protocol, utilizing no multithreading (but also for example CLI).

What is PGO?

amd64 (x86_64) Builds

PHP 7 provides full 64-bit support. The x64 builds of PHP 7 support native 64-bit integers, LFS, 64-bit memory_limit and much more.

x64 builds are recommended (almost all Windows installations support x64).

Long and multibyte path

PHP 7.1+ supports long and UTF-8 paths. See the manual for details.

Archives

Past releases are available from our archives, older versions not found there can be found at the Museum.

Missing PECL DLLs

You may have already noticed that DLLs for new PECL releases are no longer available for several months. This is because the Windows PECL build machine died, and the team is still working on the long term plan of building DLLs for PECL extensions with a new CI process. We’re doing our best to finish that as soon as possible, and keep you up to date.

PECL DLLs for PHP 8.1

A week ago PHP 8.1.0 has been released and you may be eager to try it out, but you need one or more PECL packages for which there are no PHP 8.1 binary packages available yet, and you may wonder when these will be made available. Well, the PHP for Windows team does not want to provide possibly premature binary packages, so as usual, we will wait until late January or early February to trigger the mass build for all applicable PECL packages; that is, after PHP 8.1.2 has been released, what is currently scheduled for January, 20th. After the builds have been done, you can download the binary packages from pecl.php.net as usual. Waiting for two months is no option for you? In that case you can download snapshot builds of some of the PECL packages. If there is no snapshot for your package available, consider to contact the team and to request that a snapshot for that package is being build. Note though, that these snapshot builds are not recommended for production. However, testing these and reporting issues is very welcome!

Where are the PECL DLLs?

You may have noticed already that Windows DLLs are no longer available on PECL. Since the PHP for Windows team has no access to that machine to debug the problem, the best we could do is to file a respective bug report, and to hope that it will be fixed in a timely manner. Anyhow, we keep building and monitoring the build results of all PECL packages for Windows. And you can download the DLLs from our server. Sorry for the inconvenience! PS: this issue has been resolved!

libjpeg dependency

As of PHP 8.1.0, the official Windows dependencies use libjpeg-turbo instead of libjpeg. The main reason is that libjpeg-turbo offers better performance, because it uses SIMD instructions on supported platforms (Windows x86 and x64 are supported). Note that many Linux distributions already use libjpeg-turbo for quite a while. This is relevant for the GD extension, but may affect other extensions as well. Please file a bug report, if you experience any problems regarding this change.

PHP 8 Snapshot Builds

You may have already noticed that we didn’t provide snapshot builds for PHP 8 for many months. There are no plans to change that, but users can get third party provided nighly builds. We will, of course, continue to provide Windows builds of all PHP (pre-)releases. So watch out for the release of PHP 8.1.0alpha1, scheduled for 10 Jun 2021!

OCI DLLs missing from PHP 8.0.0 pre-release builds

Due to a build system error which only has been noticed recently, so far the PHP 8.0.0 pre-release builds didn’t contain php_oci8_12c.dll and php_pdo_oci.dll in the ext/ folder. You can now separately download these files and copy them in your existing PHP-8.0.0beta1 installation (the DLLs are not suitable for the alpha releases). Make sure that you use the appropriate package (x64 vs. x86, and non thread-safe vs. thread-safe).

Windows Defender Warnings

A few days ago, we have noticed that Windows Defender reports some files in the PHP source and test packages as severe threat, claiming they would constitute a backdoor (e.g. Backdoor:PHP/Dirtelti.MTF). These files are auxiliary test files containing eval statements. Are these files backdoors? That depends on the context, i.e. in this case whether they are accessible via the Web. If they are, because they have been uploaded to the webroot of a publicly available Webserver, for instance, they may pose a serious threat. On the other hand, if they are just used on a local machine for development and testing purpuses, they are not malicious in any way. So, if you experience such Windows Defender warnings, examine the reported files, make sure they don’t pose any threat, and then unblock them. Happy PHPing on Windows!

OpenSSL default config path changed

As of PHP 7.4.0, the OpenSSL default config path changes from c:\usr\local\ssl\openssl.cnf to C:\Program Files\Common Files\SSL\openssl.conf for x64 builds, and C:\Program Files (x86)\Common Files\SSL\openssl.conf for x86 builds. These paths match the defaults of OpenSSL 1.1, and are more inline with the Windows folder structure than the old settings. Note that this path is still configurable via the environment variable OPENSSL_CONF. See also the installation section in the PHP manual.

PHP 7.4 builds use Visual Studio 2017

We used Visual Studio 2019 to build the early releases of PHP 7.4 (up to and including 7.4.0beta2). And although Visual Studio 2019 is generally an improvement over Visual Studio 2017, due to compatibility issues we have decided to switch back to Visual Studio 2017 for our PHP 7.4 builds, and we are planning to stick with this for the complete lifetime of PHP 7.4. Note that it is still possible to use Apache VS16 builds from Apachelounge in combination with PHP 7.4, since VS 2019 is forward compatible with VS 2017. Our master snapshots are still built with Visual Studio 2019, and we are planning to stick with Visual Studio 2019 for PHP 8.0.

Visual Studio 2019 Builds

All binary packages we were offering contained «vc#» (for instance, «vc14») in the filename to designate the Visual Studio version which has been used to build them. This number («#») has tradionally been the major number of the respective platform toolset. The preview releases of Visual Studio 2017 shipped with platform toolset 15.00, so we used «vc15» to mark the files. The first GA release of Visual Studio 2017, however, shipped with platform toolset 14.10 (to signal the backward compatibility), but the internal Visual Studio version number stayed 15.00. To avoid confusion with already distributed packages, we stuck with the «vc15» marker. For our Visual Studio 2019 builds (PHP 7.4 and master) we finally changed from «vc#» to «vs#» (note the «s»), where the number now designates the major internal Visual Studio version number. We are planning to stick with this new naming scheme for the foreseeable future.

Источник

Php для windows установщик

The releases are tagged and signed in the PHP Git Repository. The following official GnuPG keys of the current PHP Release Manager can be used to verify the tags:

PHP 8.2

pub rsa4096 2021-04-01 [SC] 1198 C011 7593 497A 5EC5 C199 286A F1F9 8974 69DC uid [ultimate] Pierrick Charron sub rsa4096 2021-04-01 [E] pub rsa4096 2021-04-26 [SC] [expires: 2025-11-24] 39B6 4134 3D8C 104B 2B14 6DC3 F9C3 9DC0 B969 8544 uid [ultimate] Ben Ramsey sub rsa4096 2021-04-26 [E] [expires: 2025-11-24] pub rsa4096 2021-03-26 [SC] [expires: 2030-03-26] E609 13E4 DF20 9907 D8E3 0D96 659A 97C9 CF2A 795A uid [ultimate] Sergey Panteleev uid [ultimate] Sergey Panteleev uid [ultimate] Sergey Panteleev sub rsa4096 2021-03-26 [E] [expires: 2025-03-26]

PHP 8.1

pub 2048R/31CBD89E 2016-12-08 Key fingerprint = 5289 95BF EDFB A719 1D46 839E F9BA 0ADA 31CB D89E uid Joe Watkins pub rsa4096 2021-04-26 [SC] [expires: 2025-11-24] 39B6 4134 3D8C 104B 2B14 6DC3 F9C3 9DC0 B969 8544 uid [ultimate] Ben Ramsey sub rsa4096 2021-04-26 [E] [expires: 2025-11-24] pub rsa4096 2021-04-01 [SC] F1F6 9223 8FBC 1666 E5A5 CCD4 199F 9DFE F6FF BAFD uid [ultimate] Patrick Allaert sub rsa4096 2021-04-01 [E]

PHP 8.0

pub 4096R/70D12172 2017-04-14 [expires: 2024-04-21] Key fingerprint = 1729 F839 38DA 44E2 7BA0 F4D3 DBDB 3974 70D1 2172 uid Sara Golemon pub rsa4096 2020-05-09 [SC] [expires: 2024-05-08] BFDD D286 4282 4F81 18EF 7790 9B67 A5C1 2229 118F uid [ultimate] Gabriel Caruso (Release Manager) sub rsa4096 2020-05-09 [E] [expires: 2024-05-08] pub rsa4096 2022-08-30 [SC] [expires: 2024-08-29] 2C16 C765 DBE5 4A08 8130 F1BC 4B9B 5F60 0B55 F3B4 uid [ultimate] Gabriel Caruso sub rsa4096 2022-08-30 [E] [expires: 2024-08-29]

Check the supported versions page for more information on the support lifetime of each version of PHP.

Источник

Php для windows установщик

IIS является встроенным в Windows. На сервере Windows используйте Server Manager для добавления роли IIS. Убедитесь, что функция роли CGI включена. На рабочем столе Windows используйте панель «Установка и удаление программ» для добавления IIS. В документации Microsoft есть » подробные инструкции. Для настольных веб-приложений и веб-разработки можно также использовать IIS/Express или рабочий стол PHP.

Пример #1 Командная строка для настройки IIS и PHP

@echo off REM download .ZIP file of PHP build from http://windows.php.net/downloads/ REM path to directory you decompressed PHP .ZIP file into (no trailing \) set phppath=c:\php REM Clear current PHP handlers %windir%\system32\inetsrv\appcmd clear config /section:system.webServer/fastCGI REM The following command will generate an error message if PHP is not installed. This can be ignored. %windir%\system32\inetsrv\appcmd set config /section:system.webServer/handlers /-[name='PHP_via_FastCGI'] REM Set up the PHP handler %windir%\system32\inetsrv\appcmd set config /section:system.webServer/fastCGI /+[fullPath='%phppath%\php-cgi.exe'] %windir%\system32\inetsrv\appcmd set config /section:system.webServer/handlers /+[name='PHP_via_FastCGI',path='*.php',verb='*',modules='FastCgiModule',scriptProcessor='%phppath%\php-cgi.exe',resourceType='Unspecified'] %windir%\system32\inetsrv\appcmd set config /section:system.webServer/handlers /accessPolicy:Read,Script REM Configure FastCGI Variables %windir%\system32\inetsrv\appcmd set config -section:system.webServer/fastCgi /[fullPath='%phppath%\php-cgi.exe'].instanceMaxRequests:10000 %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/fastCgi /+"[fullPath='%phppath%\php-cgi.exe'].environmentVariables.[name='PHP_FCGI_MAX_REQUESTS',value='10000']" %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/fastCgi /+"[fullPath='%phppath%\php-cgi.exe'].environmentVariables.[name='PHPRC',value='%phppath%\php.ini']"

Apache

Существует несколько версий Apache2 для Windows. Мы поддерживаем ApacheLounge, но другие варианты включают XAMPP, WampServer и BitNami, которые предоставляют средства автоматической установки. Вы можете использовать mod_php или mod_fastcgi для загрузки PHP на Apache. Если вы используете mod_php, необходимо использовать TS-build Apache, Visual C той же версии и тот же процессор (x86 или x64).

Выберите сборку

Скачайте PHP-релизы с » http://windows.php.net/download/. Все сборки оптимизированы ( PGO ), а выпуски QA и GA тщательно протестированы.

• Thread-Safe(TS) — для одного процесса веб-служб, как Apache с mod_php
• Non-Thread-Safe(NTS) — для служб IIS и других FastCGI веб-серверов (Apache с mod_fastcgi) рекомендуется и для сценариев командной строки
• для x86 — для 32-разрядной версии
• для x64 — для 64-разрядной версии

Источник