diff --git a/.travis.yml b/.travis.yml new file mode 100644 index 0000000..27f588f --- /dev/null +++ b/.travis.yml @@ -0,0 +1,23 @@ +sudo: false + +language: php +php: + - 7.0 + +before_script: + - phpenv config-rm xdebug.ini + - pecl install channel://pecl.php.net/pthreads-3.1.6 + - pecl install channel://pecl.php.net/weakref-0.3.2 + - echo | pecl install channel://pecl.php.net/yaml-2.0.0 + +script: + - ./tests/ci.sh + +notifications: + email: false + webhooks: + urls: + - https://webhooks.gitter.im/e/e51c4708fdbca6d5ee37 + on_success: change # options: [always|never|change] default: always + on_failure: always # options: [always|never|change] default: always + on_start: never # options: [always|never|change] default: always diff --git a/README.md b/README.md index e8673ca..3d9fed8 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,9 @@ # DevMine The new mcpe software that does not use pm code base! +## IMPORTANT NOTICE: +For the purpose of this Beta Program, the yml and properties files are already pasted. When it becomes stable, we will remove them. + # Why is it called DevMine? Simply because you need to understand php in order to convert PocketMine plugins into DevMine plugins! @@ -15,24 +18,24 @@ pocketmine\block --> devmine\inventory\blocks
pocketmine\item --> devmine\inventory\items
pocketmine\inventory --> devmine\inventory\layout
pocketmine\tile --> devmine\inventory\solidentity
-pocketmine\updater --> devmine\server\updater
-pocketmine\utils --> devmine\utilities\main
-pocketmine not in folder (exclude player and iplayer) --> devmine\server
-pocketmine\network --> devmine\server\network
-pocketmine\lang --> devmine\utilities\languages
-pocketmine\wizard --> devmine\utilities\installer
+pocketmine\plugin --> devmine\consumer\plugin
+pocketmine\resourcepacks --> devmine\consumer\resourcepacks
pocketmine\nbt--> devmine\creatures\player
-player.php and iplayer.php --> devmine\creatures\player
+player.php and iplayer.php and offlineplayer.php --> devmine\creatures\player
pocketmine\entity --> devmine\creatures\entities
+pocketmine not in folder (exclude player and iplayer and offlineplayer) --> devmine\server
+pocketmine\network --> devmine\server\network
+pocketmine\permission --> devmine\server\perms
+pocketmine\resources --> devmine\server\resources
+pocketmine\scheduler --> devmine\server\tasks
pocketmine\command --> devmine\server\commands
-pocketmine\plugin --> devmine\plugin-features
-pocketmine\level --> devmine\levels
-pocketmine\metadata --> devmine\server\epilogos
+pocketmine\metadata --> devmine\server\meta
pocketmine\math --> devmine\server\calculations
+pocketmine\lang --> devmine\utilities\languages
+pocketmine\wizard --> devmine\utilities\installer
+pocketmine\utils --> devmine\utilities\main
+pocketmine\level --> devmine\worlds
pocketmine\event --> devmine\events
-pocketmine\permission --> devmine\server\permissions
-pocketmine\resources --> devmine\server\resources
-pocketmine\scheduler --> devmine\server\tasks
raklib --> raklib
spl --> spl
@@ -42,20 +45,10 @@ pocketmine\tile\Tile.php --> devmine\inventory\solidentity\SolidEntity.php
pocketmine\player.php --> devmine\creatures\player\Player.php
pocketmine\iplayer.php --> devmine\creatures\player\iPlayer.php
pocketmine\OfflinePlayer.php --> devmine\creatures\player\OfflinePlayer.php
-Achievement.php -CompatibleClassLoader.php -CrashDump.php -MemoryManager.php -OfflinePlayer.php -Server.php -Thread.php -ThreadManager.php -Worker.php # THINGS TO CHANGE remove all instances of pocketmine, rename to devmine
-remove all instances of tiles, rename to solidentity -remove all instances of genysis, rename to devmine -remove all instances of scheduler, rename to tasks -remove all instances of metadata, rename to epilogos -Everybody plz tell me if any other things i need to change. +remove all instances of tiles, rename to solidentity
+remove all instances of genysis and tesseract and pocketmine, rename to devmine
+remove all instances of scheduler, rename to tasks
+remove all instances of metadata, rename to meta
diff --git a/bin/cygwin-console-helper.exe b/bin/cygwin-console-helper.exe new file mode 100644 index 0000000..221ed5d Binary files /dev/null and b/bin/cygwin-console-helper.exe differ diff --git a/bin/cygwin1.dll b/bin/cygwin1.dll new file mode 100644 index 0000000..5b4d2f5 Binary files /dev/null and b/bin/cygwin1.dll differ diff --git a/bin/mintty.exe b/bin/mintty.exe new file mode 100644 index 0000000..0e904d1 Binary files /dev/null and b/bin/mintty.exe differ diff --git a/bin/php/deplister.exe b/bin/php/deplister.exe new file mode 100644 index 0000000..d3c79d7 Binary files /dev/null and b/bin/php/deplister.exe differ diff --git a/bin/php/dev/php7ts.lib b/bin/php/dev/php7ts.lib new file mode 100644 index 0000000..b6e30a0 Binary files /dev/null and b/bin/php/dev/php7ts.lib differ diff --git a/bin/php/ext/php_bz2.dll b/bin/php/ext/php_bz2.dll new file mode 100644 index 0000000..6d8d3d0 Binary files /dev/null and b/bin/php/ext/php_bz2.dll differ diff --git a/bin/php/ext/php_com_dotnet.dll b/bin/php/ext/php_com_dotnet.dll new file mode 100644 index 0000000..0bd6394 Binary files /dev/null and b/bin/php/ext/php_com_dotnet.dll differ diff --git a/bin/php/ext/php_curl.dll b/bin/php/ext/php_curl.dll new file mode 100644 index 0000000..cea57c2 Binary files /dev/null and b/bin/php/ext/php_curl.dll differ diff --git a/bin/php/ext/php_enchant.dll b/bin/php/ext/php_enchant.dll new file mode 100644 index 0000000..9622d66 Binary files /dev/null and b/bin/php/ext/php_enchant.dll differ diff --git a/bin/php/ext/php_exif.dll b/bin/php/ext/php_exif.dll new file mode 100644 index 0000000..1c66cc1 Binary files /dev/null and b/bin/php/ext/php_exif.dll differ diff --git a/bin/php/ext/php_fileinfo.dll b/bin/php/ext/php_fileinfo.dll new file mode 100644 index 0000000..3eb2d72 Binary files /dev/null and b/bin/php/ext/php_fileinfo.dll differ diff --git a/bin/php/ext/php_ftp.dll b/bin/php/ext/php_ftp.dll new file mode 100644 index 0000000..eedde38 Binary files /dev/null and b/bin/php/ext/php_ftp.dll differ diff --git a/bin/php/ext/php_gd2.dll b/bin/php/ext/php_gd2.dll new file mode 100644 index 0000000..7ed3fbb Binary files /dev/null and b/bin/php/ext/php_gd2.dll differ diff --git a/bin/php/ext/php_gettext.dll b/bin/php/ext/php_gettext.dll new file mode 100644 index 0000000..138db2e Binary files /dev/null and b/bin/php/ext/php_gettext.dll differ diff --git a/bin/php/ext/php_gmp.dll b/bin/php/ext/php_gmp.dll new file mode 100644 index 0000000..41296d6 Binary files /dev/null and b/bin/php/ext/php_gmp.dll differ diff --git a/bin/php/ext/php_imap.dll b/bin/php/ext/php_imap.dll new file mode 100644 index 0000000..d5c0ba7 Binary files /dev/null and b/bin/php/ext/php_imap.dll differ diff --git a/bin/php/ext/php_interbase.dll b/bin/php/ext/php_interbase.dll new file mode 100644 index 0000000..145555f Binary files /dev/null and b/bin/php/ext/php_interbase.dll differ diff --git a/bin/php/ext/php_intl.dll b/bin/php/ext/php_intl.dll new file mode 100644 index 0000000..48db483 Binary files /dev/null and b/bin/php/ext/php_intl.dll differ diff --git a/bin/php/ext/php_ldap.dll b/bin/php/ext/php_ldap.dll new file mode 100644 index 0000000..05cffda Binary files /dev/null and b/bin/php/ext/php_ldap.dll differ diff --git a/bin/php/ext/php_mbstring.dll b/bin/php/ext/php_mbstring.dll new file mode 100644 index 0000000..78a327f Binary files /dev/null and b/bin/php/ext/php_mbstring.dll differ diff --git a/bin/php/ext/php_mysqli.dll b/bin/php/ext/php_mysqli.dll new file mode 100644 index 0000000..200cd52 Binary files /dev/null and b/bin/php/ext/php_mysqli.dll differ diff --git a/bin/php/ext/php_oci8_12c.dll b/bin/php/ext/php_oci8_12c.dll new file mode 100644 index 0000000..c5aa4ca Binary files /dev/null and b/bin/php/ext/php_oci8_12c.dll differ diff --git a/bin/php/ext/php_odbc.dll b/bin/php/ext/php_odbc.dll new file mode 100644 index 0000000..3d1da03 Binary files /dev/null and b/bin/php/ext/php_odbc.dll differ diff --git a/bin/php/ext/php_opcache.dll b/bin/php/ext/php_opcache.dll new file mode 100644 index 0000000..85d642a Binary files /dev/null and b/bin/php/ext/php_opcache.dll differ diff --git a/bin/php/ext/php_openssl.dll b/bin/php/ext/php_openssl.dll new file mode 100644 index 0000000..f1862ce Binary files /dev/null and b/bin/php/ext/php_openssl.dll differ diff --git a/bin/php/ext/php_pdo_firebird.dll b/bin/php/ext/php_pdo_firebird.dll new file mode 100644 index 0000000..b19e157 Binary files /dev/null and b/bin/php/ext/php_pdo_firebird.dll differ diff --git a/bin/php/ext/php_pdo_mysql.dll b/bin/php/ext/php_pdo_mysql.dll new file mode 100644 index 0000000..af8b21b Binary files /dev/null and b/bin/php/ext/php_pdo_mysql.dll differ diff --git a/bin/php/ext/php_pdo_oci.dll b/bin/php/ext/php_pdo_oci.dll new file mode 100644 index 0000000..8cfc3b0 Binary files /dev/null and b/bin/php/ext/php_pdo_oci.dll differ diff --git a/bin/php/ext/php_pdo_odbc.dll b/bin/php/ext/php_pdo_odbc.dll new file mode 100644 index 0000000..62da60e Binary files /dev/null and b/bin/php/ext/php_pdo_odbc.dll differ diff --git a/bin/php/ext/php_pdo_pgsql.dll b/bin/php/ext/php_pdo_pgsql.dll new file mode 100644 index 0000000..2e24dfa Binary files /dev/null and b/bin/php/ext/php_pdo_pgsql.dll differ diff --git a/bin/php/ext/php_pdo_sqlite.dll b/bin/php/ext/php_pdo_sqlite.dll new file mode 100644 index 0000000..02f74bd Binary files /dev/null and b/bin/php/ext/php_pdo_sqlite.dll differ diff --git a/bin/php/ext/php_pgsql.dll b/bin/php/ext/php_pgsql.dll new file mode 100644 index 0000000..4ba758a Binary files /dev/null and b/bin/php/ext/php_pgsql.dll differ diff --git a/bin/php/ext/php_phpdbg_webhelper.dll b/bin/php/ext/php_phpdbg_webhelper.dll new file mode 100644 index 0000000..9dda997 Binary files /dev/null and b/bin/php/ext/php_phpdbg_webhelper.dll differ diff --git a/bin/php/ext/php_pthreads.dll b/bin/php/ext/php_pthreads.dll new file mode 100644 index 0000000..c315a2e Binary files /dev/null and b/bin/php/ext/php_pthreads.dll differ diff --git a/bin/php/ext/php_shmop.dll b/bin/php/ext/php_shmop.dll new file mode 100644 index 0000000..c47a55d Binary files /dev/null and b/bin/php/ext/php_shmop.dll differ diff --git a/bin/php/ext/php_snmp.dll b/bin/php/ext/php_snmp.dll new file mode 100644 index 0000000..b0328e1 Binary files /dev/null and b/bin/php/ext/php_snmp.dll differ diff --git a/bin/php/ext/php_soap.dll b/bin/php/ext/php_soap.dll new file mode 100644 index 0000000..2b2da43 Binary files /dev/null and b/bin/php/ext/php_soap.dll differ diff --git a/bin/php/ext/php_sockets.dll b/bin/php/ext/php_sockets.dll new file mode 100644 index 0000000..0d6f098 Binary files /dev/null and b/bin/php/ext/php_sockets.dll differ diff --git a/bin/php/ext/php_sqlite3.dll b/bin/php/ext/php_sqlite3.dll new file mode 100644 index 0000000..9106bb3 Binary files /dev/null and b/bin/php/ext/php_sqlite3.dll differ diff --git a/bin/php/ext/php_sysvshm.dll b/bin/php/ext/php_sysvshm.dll new file mode 100644 index 0000000..9f376e9 Binary files /dev/null and b/bin/php/ext/php_sysvshm.dll differ diff --git a/bin/php/ext/php_tidy.dll b/bin/php/ext/php_tidy.dll new file mode 100644 index 0000000..7972b27 Binary files /dev/null and b/bin/php/ext/php_tidy.dll differ diff --git a/bin/php/ext/php_weakref.dll b/bin/php/ext/php_weakref.dll new file mode 100644 index 0000000..2ecae1a Binary files /dev/null and b/bin/php/ext/php_weakref.dll differ diff --git a/bin/php/ext/php_xmlrpc.dll b/bin/php/ext/php_xmlrpc.dll new file mode 100644 index 0000000..1cdf13d Binary files /dev/null and b/bin/php/ext/php_xmlrpc.dll differ diff --git a/bin/php/ext/php_xsl.dll b/bin/php/ext/php_xsl.dll new file mode 100644 index 0000000..c3d4179 Binary files /dev/null and b/bin/php/ext/php_xsl.dll differ diff --git a/bin/php/ext/php_yaml.dll b/bin/php/ext/php_yaml.dll new file mode 100644 index 0000000..a721437 Binary files /dev/null and b/bin/php/ext/php_yaml.dll differ diff --git a/bin/php/extras/ssl/openssl.cnf b/bin/php/extras/ssl/openssl.cnf new file mode 100644 index 0000000..1eb86c4 --- /dev/null +++ b/bin/php/extras/ssl/openssl.cnf @@ -0,0 +1,350 @@ +# +# OpenSSL example configuration file. +# This is mostly being used for generation of certificate requests. +# + +# This definition stops the following lines choking if HOME isn't +# defined. +HOME = . +RANDFILE = $ENV::HOME/.rnd + +# Extra OBJECT IDENTIFIER info: +#oid_file = $ENV::HOME/.oid +oid_section = new_oids + +# To use this configuration file with the "-extfile" option of the +# "openssl x509" utility, name here the section containing the +# X.509v3 extensions to use: +# extensions = +# (Alternatively, use a configuration file that has only +# X.509v3 extensions in its main [= default] section.) + +[ new_oids ] + +# We can add new OIDs in here for use by 'ca', 'req' and 'ts'. +# Add a simple OID like this: +# testoid1=1.2.3.4 +# Or use config file substitution like this: +# testoid2=${testoid1}.5.6 + +# Policies used by the TSA examples. +tsa_policy1 = 1.2.3.4.1 +tsa_policy2 = 1.2.3.4.5.6 +tsa_policy3 = 1.2.3.4.5.7 + +#################################################################### +[ ca ] +default_ca = CA_default # The default ca section + +#################################################################### +[ CA_default ] + +dir = ./demoCA # Where everything is kept +certs = $dir/certs # Where the issued certs are kept +crl_dir = $dir/crl # Where the issued crl are kept +database = $dir/index.txt # database index file. +#unique_subject = no # Set to 'no' to allow creation of + # several ctificates with same subject. +new_certs_dir = $dir/newcerts # default place for new certs. + +certificate = $dir/cacert.pem # The CA certificate +serial = $dir/serial # The current serial number +crlnumber = $dir/crlnumber # the current crl number + # must be commented out to leave a V1 CRL +crl = $dir/crl.pem # The current CRL +private_key = $dir/private/cakey.pem# The private key +RANDFILE = $dir/private/.rand # private random number file + +x509_extensions = usr_cert # The extentions to add to the cert + +# Comment out the following two lines for the "traditional" +# (and highly broken) format. +name_opt = ca_default # Subject Name options +cert_opt = ca_default # Certificate field options + +# Extension copying option: use with caution. +# copy_extensions = copy + +# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs +# so this is commented out by default to leave a V1 CRL. +# crlnumber must also be commented out to leave a V1 CRL. +# crl_extensions = crl_ext + +default_days = 365 # how long to certify for +default_crl_days= 30 # how long before next CRL +default_md = default # use public key default MD +preserve = no # keep passed DN ordering + +# A few difference way of specifying how similar the request should look +# For type CA, the listed attributes must be the same, and the optional +# and supplied fields are just that :-) +policy = policy_match + +# For the CA policy +[ policy_match ] +countryName = match +stateOrProvinceName = match +organizationName = match +organizationalUnitName = optional +commonName = supplied +emailAddress = optional + +# For the 'anything' policy +# At this point in time, you must list all acceptable 'object' +# types. +[ policy_anything ] +countryName = optional +stateOrProvinceName = optional +localityName = optional +organizationName = optional +organizationalUnitName = optional +commonName = supplied +emailAddress = optional + +#################################################################### +[ req ] +default_bits = 2048 +default_keyfile = privkey.pem +distinguished_name = req_distinguished_name +attributes = req_attributes +x509_extensions = v3_ca # The extentions to add to the self signed cert + +# Passwords for private keys if not present they will be prompted for +# input_password = secret +# output_password = secret + +# This sets a mask for permitted string types. There are several options. +# default: PrintableString, T61String, BMPString. +# pkix : PrintableString, BMPString (PKIX recommendation before 2004) +# utf8only: only UTF8Strings (PKIX recommendation after 2004). +# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings). +# MASK:XXXX a literal mask value. +# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings. +string_mask = utf8only + +# req_extensions = v3_req # The extensions to add to a certificate request + +[ req_distinguished_name ] +countryName = Country Name (2 letter code) +countryName_default = AU +countryName_min = 2 +countryName_max = 2 + +stateOrProvinceName = State or Province Name (full name) +stateOrProvinceName_default = Some-State + +localityName = Locality Name (eg, city) + +0.organizationName = Organization Name (eg, company) +0.organizationName_default = Internet Widgits Pty Ltd + +# we can do this but it is not needed normally :-) +#1.organizationName = Second Organization Name (eg, company) +#1.organizationName_default = World Wide Web Pty Ltd + +organizationalUnitName = Organizational Unit Name (eg, section) +#organizationalUnitName_default = + +commonName = Common Name (e.g. server FQDN or YOUR name) +commonName_max = 64 + +emailAddress = Email Address +emailAddress_max = 64 + +# SET-ex3 = SET extension number 3 + +[ req_attributes ] +challengePassword = A challenge password +challengePassword_min = 4 +challengePassword_max = 20 + +unstructuredName = An optional company name + +[ usr_cert ] + +# These extensions are added when 'ca' signs a request. + +# This goes against PKIX guidelines but some CAs do it and some software +# requires this to avoid interpreting an end user certificate as a CA. + +basicConstraints=CA:FALSE + +# Here are some examples of the usage of nsCertType. If it is omitted +# the certificate can be used for anything *except* object signing. + +# This is OK for an SSL server. +# nsCertType = server + +# For an object signing certificate this would be used. +# nsCertType = objsign + +# For normal client use this is typical +# nsCertType = client, email + +# and for everything including object signing: +# nsCertType = client, email, objsign + +# This is typical in keyUsage for a client certificate. +# keyUsage = nonRepudiation, digitalSignature, keyEncipherment + +# This will be displayed in Netscape's comment listbox. +nsComment = "OpenSSL Generated Certificate" + +# PKIX recommendations harmless if included in all certificates. +subjectKeyIdentifier=hash +authorityKeyIdentifier=keyid,issuer + +# This stuff is for subjectAltName and issuerAltname. +# Import the email address. +# subjectAltName=email:copy +# An alternative to produce certificates that aren't +# deprecated according to PKIX. +# subjectAltName=email:move + +# Copy subject details +# issuerAltName=issuer:copy + +#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem +#nsBaseUrl +#nsRevocationUrl +#nsRenewalUrl +#nsCaPolicyUrl +#nsSslServerName + +# This is required for TSA certificates. +# extendedKeyUsage = critical,timeStamping + +[ v3_req ] + +# Extensions to add to a certificate request + +basicConstraints = CA:FALSE +keyUsage = nonRepudiation, digitalSignature, keyEncipherment + +[ v3_ca ] + + +# Extensions for a typical CA + + +# PKIX recommendation. + +subjectKeyIdentifier=hash + +authorityKeyIdentifier=keyid:always,issuer + +# This is what PKIX recommends but some broken software chokes on critical +# extensions. +#basicConstraints = critical,CA:true +# So we do this instead. +basicConstraints = CA:true + +# Key usage: this is typical for a CA certificate. However since it will +# prevent it being used as an test self-signed certificate it is best +# left out by default. +# keyUsage = cRLSign, keyCertSign + +# Some might want this also +# nsCertType = sslCA, emailCA + +# Include email address in subject alt name: another PKIX recommendation +# subjectAltName=email:copy +# Copy issuer details +# issuerAltName=issuer:copy + +# DER hex encoding of an extension: beware experts only! +# obj=DER:02:03 +# Where 'obj' is a standard or added object +# You can even override a supported extension: +# basicConstraints= critical, DER:30:03:01:01:FF + +[ crl_ext ] + +# CRL extensions. +# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL. + +# issuerAltName=issuer:copy +authorityKeyIdentifier=keyid:always + +[ proxy_cert_ext ] +# These extensions should be added when creating a proxy certificate + +# This goes against PKIX guidelines but some CAs do it and some software +# requires this to avoid interpreting an end user certificate as a CA. + +basicConstraints=CA:FALSE + +# Here are some examples of the usage of nsCertType. If it is omitted +# the certificate can be used for anything *except* object signing. + +# This is OK for an SSL server. +# nsCertType = server + +# For an object signing certificate this would be used. +# nsCertType = objsign + +# For normal client use this is typical +# nsCertType = client, email + +# and for everything including object signing: +# nsCertType = client, email, objsign + +# This is typical in keyUsage for a client certificate. +# keyUsage = nonRepudiation, digitalSignature, keyEncipherment + +# This will be displayed in Netscape's comment listbox. +nsComment = "OpenSSL Generated Certificate" + +# PKIX recommendations harmless if included in all certificates. +subjectKeyIdentifier=hash +authorityKeyIdentifier=keyid,issuer + +# This stuff is for subjectAltName and issuerAltname. +# Import the email address. +# subjectAltName=email:copy +# An alternative to produce certificates that aren't +# deprecated according to PKIX. +# subjectAltName=email:move + +# Copy subject details +# issuerAltName=issuer:copy + +#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem +#nsBaseUrl +#nsRevocationUrl +#nsRenewalUrl +#nsCaPolicyUrl +#nsSslServerName + +# This really needs to be in place for it to be a proxy certificate. +proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo + +#################################################################### +[ tsa ] + +default_tsa = tsa_config1 # the default TSA section + +[ tsa_config1 ] + +# These are used by the TSA reply generation only. +dir = ./demoCA # TSA root directory +serial = $dir/tsaserial # The current serial number (mandatory) +crypto_device = builtin # OpenSSL engine to use for signing +signer_cert = $dir/tsacert.pem # The TSA signing certificate + # (optional) +certs = $dir/cacert.pem # Certificate chain to include in reply + # (optional) +signer_key = $dir/private/tsakey.pem # The TSA private key (optional) + +default_policy = tsa_policy1 # Policy if request did not specify it + # (optional) +other_policies = tsa_policy2, tsa_policy3 # acceptable policies (optional) +digests = md5, sha1 # Acceptable message digests (mandatory) +accuracy = secs:1, millisecs:500, microsecs:100 # (optional) +clock_precision_digits = 0 # number of digits after dot. (optional) +ordering = yes # Is ordering defined for timestamps? + # (optional, default: no) +tsa_name = yes # Must the TSA name be included in the reply? + # (optional, default: no) +ess_cert_id_chain = no # Must the ESS cert id chain be included? + # (optional, default: no) diff --git a/bin/php/glib-2.dll b/bin/php/glib-2.dll new file mode 100644 index 0000000..9dac826 Binary files /dev/null and b/bin/php/glib-2.dll differ diff --git a/bin/php/gmodule-2.dll b/bin/php/gmodule-2.dll new file mode 100644 index 0000000..005eefd Binary files /dev/null and b/bin/php/gmodule-2.dll differ diff --git a/bin/php/icudt57.dll b/bin/php/icudt57.dll new file mode 100644 index 0000000..72433a8 Binary files /dev/null and b/bin/php/icudt57.dll differ diff --git a/bin/php/icuin57.dll b/bin/php/icuin57.dll new file mode 100644 index 0000000..d57005e Binary files /dev/null and b/bin/php/icuin57.dll differ diff --git a/bin/php/icuio57.dll b/bin/php/icuio57.dll new file mode 100644 index 0000000..9769c07 Binary files /dev/null and b/bin/php/icuio57.dll differ diff --git a/bin/php/icule57.dll b/bin/php/icule57.dll new file mode 100644 index 0000000..9d06741 Binary files /dev/null and b/bin/php/icule57.dll differ diff --git a/bin/php/iculx57.dll b/bin/php/iculx57.dll new file mode 100644 index 0000000..66d3403 Binary files /dev/null and b/bin/php/iculx57.dll differ diff --git a/bin/php/icuuc57.dll b/bin/php/icuuc57.dll new file mode 100644 index 0000000..09a7b8b Binary files /dev/null and b/bin/php/icuuc57.dll differ diff --git a/bin/php/install.txt b/bin/php/install.txt new file mode 100644 index 0000000..be87921 --- /dev/null +++ b/bin/php/install.txt @@ -0,0 +1,1797 @@ +Installing PHP + __________________________________________________________________ + + Table of Contents + Preface + 1. General Installation Considerations + 2. Installation on Windows systems + + Manual Installation Steps + ActiveScript + Microsoft IIS + Apache 1.3.x on Microsoft Windows + Apache 2.0.x on Microsoft Windows + Sun, iPlanet and Netscape servers on Microsoft Windows + OmniHTTPd Server + Sambar Server on Microsoft Windows + Xitami on Microsoft Windows + Installation of extensions on Windows + + 3. Installation of PECL extensions + + Introduction to PECL Installations + Downloading PECL extensions + PECL for Windows users + Compiling shared PECL extensions with the pecl command + Compiling shared PECL extensions with phpize + Compiling PECL extensions statically into PHP + + 4. Problems? + + Read the FAQ + Other problems + Bug reports + + 5. Runtime Configuration + + The configuration file + How to change configuration settings + + 6. Installation FAQ + __________________________________________________________________ + +Preface + + These installation instructions were generated from the HTML version of + the PHP Manual so formatting and linking have been altered. See the + online and updated version at: http://php.net/install.windows + __________________________________________________________________ + +Chapter 1. General Installation Considerations + + Before starting the installation, first you need to know what do you + want to use PHP for. There are three main fields you can use PHP, as + described in the What can PHP do? section: + + * Websites and web applications (server-side scripting) + * Command line scripting + * Desktop (GUI) applications + + For the first and most common form, you need three things: PHP itself, + a web server and a web browser. You probably already have a web + browser, and depending on your operating system setup, you may also + have a web server (e.g. Apache on Linux and MacOS X; IIS on Windows). + You may also rent webspace at a company. This way, you don't need to + set up anything on your own, only write your PHP scripts, upload it to + the server you rent, and see the results in your browser. + + In case of setting up the server and PHP on your own, you have two + choices for the method of connecting PHP to the server. For many + servers PHP has a direct module interface (also called SAPI). These + servers include Apache, Microsoft Internet Information Server, Netscape + and iPlanet servers. Many other servers have support for ISAPI, the + Microsoft module interface (OmniHTTPd for example). If PHP has no + module support for your web server, you can always use it as a CGI or + FastCGI processor. This means you set up your server to use the CGI + executable of PHP to process all PHP file requests on the server. + + If you are also interested to use PHP for command line scripting (e.g. + write scripts autogenerating some images for you offline, or processing + text files depending on some arguments you pass to them), you always + need the command line executable. For more information, read the + section about writing command line PHP applications. In this case, you + need no server and no browser. + + With PHP you can also write desktop GUI applications using the PHP-GTK + extension. This is a completely different approach than writing web + pages, as you do not output any HTML, but manage Windows and objects + within them. For more information about PHP-GTK, please visit the site + dedicated to this extension. PHP-GTK is not included in the official + PHP distribution. + + From now on, this section deals with setting up PHP for web servers on + Unix and Windows with server module interfaces and CGI executables. You + will also find information on the command line executable in the + following sections. + + PHP source code and binary distributions for Windows can be found at + http://www.php.net/downloads.php. We recommend you to choose a mirror + nearest to you for downloading the distributions. + __________________________________________________________________ + +Chapter 2. Installation on Windows systems + + This section applies to Windows 98/Me and Windows NT/2000/XP/2003. PHP + will not work on 16 bit platforms such as Windows 3.1 and sometimes we + refer to the supported Windows platforms as Win32. Windows 95 is no + longer supported as of PHP 4.3.0. + + If you have Microsoft Visual Studio, you can also build PHP from the + original source code. + + Once you have PHP installed on your Windows system, you may also want + to load various extensions for added functionality. + + Warning + + There are several all-in-one installers over the Internet, but none of + those are endorsed by PHP.net, as we believe that the manual + installation is the best choice to have your system secure and + optimised. + __________________________________________________________________ + +Manual Installation Steps + + This install guide will help you manually install and configure PHP + with a web server on Microsoft Windows. To get started you'll need to + download the zip binary distribution from the downloads page at + http://www.php.net/downloads.php. + + Although there are many all-in-one installation kits, we recommend you + take the time to setup PHP yourself as this will provide you with a + better understanding of the system, and enables you to install PHP + extensions easily when needed. + + Upgrading from a previous PHP version: Previous editions of the + manual suggest moving various ini and DLL files into your SYSTEM + (i.e. C:\WINDOWS) folder and while this simplifies the installation + procedure it makes upgrading difficult. We advise you remove all of + these files (like php.ini and PHP related DLLs from the Windows + SYSTEM folder) before moving on with a new PHP installation. Be sure + to backup these files as you might break the entire system. The old + php.ini might be useful in setting up the new PHP as well. And as + you'll soon learn, the preferred method for installing PHP is to + keep all PHP related files in one directory and have this directory + available to your systems PATH. + + MDAC requirements: If you use Microsoft Windows 98/NT4 download the + latest version of the Microsoft Data Access Components (MDAC) for + your platform. MDAC is available at http://msdn.microsoft.com/data/. + This requirement exists because ODBC is built into the distributed + Windows binaries. + + The following steps should be completed on all installations before any + server specific instructions are performed: + + Extract the distribution file into a directory of your choice. If you + are installing PHP 4, extract to C:\, as the zip file expands to a + foldername like php-4.3.7-Win32. If you are installing PHP 7, extract + to C:\php as the zip file doesn't expand as in PHP 4. You may choose a + different location but do not have spaces in the path (like C:\Program + Files\PHP) as some web servers will crash if you do. + + The directory structure extracted from the zip is different for PHP + versions 4 and 5 and look like as follows: + + Example 2-2. PHP 7 package structure +c:\php + | + +--dev + | | + | |-php7ts.lib + | + +--ext -- extension DLLs for PHP + | | + | |-php_bz2.dll + | | + | |-php_cpdf.dll + | | + | |-.. + | + +--extras + | | + | +--mibs -- support files for SNMP + | | + | +--openssl -- support files for Openssl + | | + | +--pdf-related -- support files for PDF + | | + | |-mime.magic + | + +--pear -- initial copy of PEAR + | + | + |-go-pear.bat -- PEAR setup script + | + |-fdftk.dll + | + |-.. + | + |-php-cgi.exe -- CGI executable + | + |-php-win.exe -- executes scripts without an opened command prompt + | + |-php.exe -- CLI executable - ONLY for command line scripting + | + |-.. + | + |-php.ini-development -- development php.ini settings + | + |-php.ini-production -- recommended php.ini settings for production + | + |-php5activescript.dll + | + |-php7apache2_4.dll + | + |-.. + | + |-php5ts.dll -- core PHP DLL + | + |-... + + Notice the differences and similarities. Both PHP 4 and PHP 5 have a + CGI executable, a CLI executable, and server modules, but they are + located in different folders and/or have different names. While PHP 4 + packages have the server modules in the sapi folder, PHP 5 + distributions have no such directory and instead they're in the PHP + folder root. The supporting DLLs for the PHP 5 extensions are also not + in a separate directory. + + Note: In PHP 4, you should move all files located in the dll and + sapi folders to the main folder (e.g. C:\php). + + Here is a list of server modules shipped with PHP 5: + + * php7apache2_4.dll - Apache 2.4.x module. + + Server modules provide significantly better performance and additional + functionality compared to the CGI binary. The FastCGI is significantly + more stable and can be faster than the ISAPI module with IIS. + The CLI version is designed to let you use PHP for command line + scripting. More information about CLI is available in the chapter + about using PHP from the command line. + + Warning + + The SAPI modules have been significantly improved as of the 4.1 + release, however, in older systems you may encounter server errors or + other server modules failing, such as ASP. + + The CGI and CLI binaries, and the web server modules all require the + php7ts.dll file to be available to them. You have to make + sure that this file can be found by your PHP installation. The search + order for this DLL is as follows: + + * The same directory from where php.exe is called, or in case you use + a SAPI module, the web server's directory (e.g. C:\Program + Files\Apache Group\Apache2\bin). + * Any directory in your Windows PATH environment variable. + + To make php7ts.dll available you have three options: copy + the file to the Windows system directory, copy the file to the web + server's directory, or add your PHP directory, C:\php to the PATH. For + better maintenance, we advise you to follow the last option, add C:\php + to the PATH, because it will be simpler to upgrade PHP in the future. + Read more about how to add your PHP directory to PATH in the + corresponding FAQ entry (and then don't forget to restart the computer + - logoff isn't enough). + + The next step is to set up a valid configuration file for PHP, php.ini. + There are two ini files distributed in the zip file, php.ini-development + and php.ini-production. We advise you to use php.ini-production, + because we optimized the default settings in this file for performance, + and security. Read this well documented file carefully because it has + changes from php.ini-production that will drastically affect your setup. + Some examples are display_errors being off and magic_quotes_gpc being off. + In addition to reading these, study the ini settings and set every + element manually yourself. If you would like to achieve the best + security, then this is the way for you, although PHP works fine with + these default ini files. Copy your chosen ini-file to a directory that + PHP is able to find and rename it to php.ini. PHP searches for php.ini + in the locations described in the Section called The configuration file + in Chapter 5 section. + + If you are running Apache 2, the simpler option is to use the PHPIniDir + directive (read the installation on Apache 2 page), otherwise your best + option is to set the PHPRC environment variable. This process is + explained in the following FAQ entry. + + Note: If you're using NTFS on Windows NT, 2000, XP or 2003, make + sure that the user running the web server has read permissions to + your php.ini (e.g. make it readable by Everyone). + + The following steps are optional: + + * Edit your new php.ini file. If you plan to use OmniHTTPd, do not + follow the next step. Set the doc_root to point to your web servers + document_root. For example: + +doc_root = c:\inetpub\wwwroot // for IIS + +doc_root = c:\apache\htdocs // for Apache + + * Choose the extensions you would like to load when PHP starts. See + the section about Windows extensions, about how to set up one, and + what is already built in. Note that on a new installation it is + advisable to first get PHP working and tested without any + extensions before enabling them in php.ini. + + PHP is now setup on your system. The next step is to choose a web + server, and enable it to run PHP. Choose a web server from the table of + contents. + __________________________________________________________________ + +ActiveScript + + This section contains notes specific to the ActiveScript installation. + + ActiveScript is a Windows only SAPI that enables you to use PHP script + in any ActiveScript compliant host, like Windows Script Host, + ASP/ASP.NET, Windows Script Components or Microsoft Scriptlet control. + + As of PHP 5.0.1, ActiveScript has been moved to the PECL repository. + The DLL for this PECL extension may be downloaded from either the PHP + Downloads page or from http://pecl4win.php.net/ + + Note: You should read the manual installation steps first! + + After installing PHP, you should download the ActiveScript DLL + (php7activescript.dll) and place it in the main PHP folder (e.g. + C:\php). + + After having all the files needed, you must register the DLL on your + system. To achieve this, open a Command Prompt window (located in the + Start Menu). Then go to your PHP directory by typing something like cd + C:\php. To register the DLL just type regsvr32 php7activescript.dll. + + To test if ActiveScript is working, create a new file, named test.wsf + (the extension is very important) and type: + + + + + + + Save and double-click on the file. If you receive a little window + saying "Hello World!" you're done. + + Note: In PHP 4, the engine was named 'ActivePHP', so if you are + using PHP 4, you should replace 'PHPScript' with 'ActivePHP' in the + above example. + + Note: ActiveScript doesn't use the default php.ini file. Instead, it + will look only in the same directory as the .exe that caused it to + load. You should create php-activescript.ini and place it in that + folder, if you wish to load extensions, etc. + __________________________________________________________________ + +Microsoft IIS + + This section contains notes and hints specific to IIS (Microsoft + Internet Information Server). + + Warning + + By using the CGI setup, your server is open to several possible + attacks. Please read our CGI security section to learn how to defend + yourself from those attacks. + __________________________________________________________________ + +General considerations for all installations of PHP with IIS + + * First, read the Manual Installation Instructions. Do not skip this + step as it provides crucial information for installing PHP on + Windows. + * CGI users must set the cgi.force_redirect PHP directive to 0 inside + php.ini. Read the faq on cgi.force_redirect for important details. + Also, CGI users may want to set the cgi.redirect_status_env + directive. When using directives, be sure these directives aren't + commented out inside php.ini. + * The PHP 4 CGI is named php.exe while in PHP 7 it's php-cgi.exe. In + PHP 7, php.exe is the CLI, and not the CGI. + * Modify the Windows PATH environment variable to include the PHP + directory. This way the PHP DLL files and PHP executables can all + remain in the PHP directory without cluttering up the Windows + system directory. For more details, see the FAQ on Setting the + PATH. + * The IIS user (usually IUSR_MACHINENAME) needs permission to read + various files and directories, such as php.ini, docroot, and the + session tmp directory. + * Be sure the extension_dir and doc_root PHP directives are + appropriately set in php.ini. These directives depend on the system + that PHP is being installed on. In PHP 4, the extension_dir is + extensions while with PHP 7 it's ext. So, an example PHP 7 + extensions_dir value is "c:\php\ext" and an example IIS doc_root + value is "c:\Inetpub\wwwroot". + * PHP extension DLL files, such as php_mysql.dll and php_curl.dll, + are found in the zip package of the PHP download. In PHP 7, many + extensions are part of PECL and can be downloaded in the + "Collection of PECL modules" package. Files such as php_zip.dll and + php_ssh2.dll. Download PHP files here. + * When defining the executable, the 'check that file exists' box may + also be checked. For a small performance penalty, the IIS + will check that the script file exists and sort out authentication + before firing up PHP. This means that the web server will provide + sensible 404 style error messages instead of CGI errors complaining + that PHP did not output any data. + __________________________________________________________________ + +Windows NT/200x/XP and IIS 4 or newer + + PHP may be installed as a CGI binary, or with the ISAPI module. In + either case, you need to start the Microsoft Management Console (may + appear as 'Internet Services Manager', either in your Windows NT 4.0 + Option Pack branch or the Control Panel=>Administrative Tools under + Windows 2000/XP). Then right click on your Web server node (this will + most probably appear as 'Default Web Server'), and select 'Properties'. + + If you want to use the CGI binary, do the following: + + * Under 'Home Directory', 'Virtual Directory', or 'Directory', do the + following: + * Change the Execute Permissions to 'Scripts only' + * Click on the 'Configuration' button, and choose the Application + Mappings tab. Click Add and set the Executable path to the + appropriate CGI file. An example PHP 7 value is: C:\php\php-cgi.exe + Supply .php as the extension. Leave 'Method exclusions' blank, and + check the 'Script engine' checkbox. Now, click OK a few times. + * Set up the appropriate security. (This is done in Internet Service + Manager), and if your NT Server uses NTFS file system, add execute + rights for I_USR_ to the directory that contains php.exe / + php-cgi.exe. + + To use the ISAPI module, do the following: + + * If you don't want to perform HTTP Authentication using PHP, you can + (and should) skip this step. Under ISAPI Filters, add a new ISAPI + filter. Use PHP as the filter name, and supply a path to the + php7isapi.dll. + * Under 'Home Directory', 'Virtual Directory', or 'Directory', do the + following: + * Change the Execute Permissions to 'Scripts only' + * Click on the 'Configuration' button, and choose the Application + Mappings tab. Click Add and set the Executable path to the + appropriate ISAPI DLL. An example PHP 7 value is: + C:\php\php7isapi.dll Supply .php as the extension. Leave 'Method + exclusions' blank, and check the 'Script engine' checkbox. Now, + click OK a few times. + * Stop IIS completely (NET STOP iisadmin) + * Start IIS again (NET START w3svc) + + With IIS 6 (2003 Server), open up the IIS Manager, go to Web Service + Extensions, choose "Add a new Web service extension", enter in a name + such as PHP, choose the Add button and for the value browse to either + the ISAPI file (php7isapi.dll) or CGI (php.exe or + php-cgi.exe) then check "Set extension status to Allowed" and click OK. + + In order to use index.php as a default content page, do the following: + From within the Documents tab, choose Add. Type in index.php and click + OK. Adjust the order by choosing Move Up or Move Down. This is similar + to setting DirectoryIndex with Apache. + + The steps above must be repeated for each extension that is to be + associated with PHP scripts. .php is the most common although .php3 may + be required for legacy applications. + + If you experience 100% CPU usage after some time, turn off the IIS + setting Cache ISAPI Application. + __________________________________________________________________ + +Windows and IIS + +See http://www.php.net/install.windows + __________________________________________________________________ + +Apache 1.3.x on Microsoft Windows + + This section contains notes and hints specific to Apache 1.3.x installs + of PHP on Microsoft Windows systems. There are also instructions and + notes for Apache 2 on a separate page. + + Note: Please read the manual installation steps first! + + There are two ways to set up PHP to work with Apache 1.3.x on Windows. + One is to use the CGI binary (php.exe for PHP 4 and php-cgi.exe for PHP + 5), the other is to use the Apache Module DLL. In either case you need + to edit your httpd.conf to configure Apache to work with PHP, and then + restart the server. + + It is worth noting here that now the SAPI module has been made more + stable under Windows, we recommend it's use above the CGI binary, since + it is more transparent and secure. + + Although there can be a few variations of configuring PHP under Apache, + these are simple enough to be used by the newcomer. Please consult the + Apache Documentation for further configuration directives. + + After changing the configuration file, remember to restart the server, + for example, NET STOP APACHE followed by NET START APACHE, if you run + Apache as a Windows Service, or use your regular shortcuts. + + Note: Remember that when adding path values in the Apache + configuration files on Windows, all backslashes such as + c:\directory\file.ext must be converted to forward slashes, as + c:/directory/file.ext. A trailing slash may also be necessary for + directories. + __________________________________________________________________ + +Installing as an Apache module + + You should add the following lines to your Apache httpd.conf file: + + Example 2-3. PHP as an Apache 1.3.x module + + This assumes PHP is installed to c:\php. Adjust the path if this is not + the case. + + For PHP 7: +# Add to the end of the LoadModule section +LoadModule php7_module "C:/php/php7apache.dll" + +# Add to the end of the AddModule section +AddModule mod_php7.c + + For both: +# Add this line inside the conditional brace +AddType application/x-httpd-php .php + +# For syntax highlighted .phps files, also add +AddType application/x-httpd-php-source .phps + __________________________________________________________________ + +Installing as a CGI binary + + If you unzipped the PHP package to C:\php\ as described in the Manual + Installation Steps section, you need to insert these lines to your + Apache configuration file to set up the CGI binary: + + Example 2-4. PHP and Apache 1.3.x as CGI +ScriptAlias /php/ "c:/php/" +AddType application/x-httpd-php .php + +# For PHP 4 +Action application/x-httpd-php "/php/php.exe" + +# For PHP 7 +Action application/x-httpd-php "/php/php-cgi.exe" + +# specify the directory where php.ini is +SetEnv PHPRC C:/php + + Note that the second line in the list above can be found in the actual + versions of httpd.conf, but it is commented out. Remember also to + substitute the c:/php/ for your actual path to PHP. + + Warning + + By using the CGI setup, your server is open to several possible + attacks. Please read our CGI security section to learn how to defend + yourself from those attacks. + + If you would like to present PHP source files syntax highlighted, there + is no such convenient option as with the module version of PHP. If you + chose to configure Apache to use PHP as a CGI binary, you will need to + use the highlight_file() function. To do this simply create a PHP + script file and add this code: . + __________________________________________________________________ + +Apache 2.0.x on Microsoft Windows + + This section contains notes and hints specific to Apache 2.0.x installs + of PHP on Microsoft Windows systems. We also have instructions and + notes for Apache 1.3.x users on a separate page. + + Note: You should read the manual installation steps first! + + Apache 2.2.x Support: Users of Apache 2.2.x may use the + documentation below except the appropriate DLL file is named + php7apache2_2.dll and it only exists as of PHP 7.2.0. See also + http://snaps.php.net/ + + Warning + + We do not recommend using a threaded MPM in production with Apache2. + Use the prefork MPM instead, or use Apache1. For information on why, + read the related FAQ entry on using Apache2 with a threaded MPM + + You are highly encouraged to take a look at the Apache Documentation to + get a basic understanding of the Apache 2.0.x Server. Also consider to + read the Windows specific notes for Apache 2.0.x before reading on + here. + + PHP and Apache 2.0.x compatibility notes: The following versions of + PHP are known to work with the most recent version of Apache 2.0.x: + + * PHP 4.3.0 or later available at http://www.php.net/downloads.php. + * the latest stable development version. Get the source code + http://snaps.php.net/php7-latest.tar.gz or download binaries for + Windows http://snaps.php.net/win32/php7-win32-latest.zip. + * a prerelease version downloadable from http://qa.php.net/. + * you have always the option to obtain PHP through SVN. + + These versions of PHP are compatible to Apache 2.0.40 and later. + + Apache 2.0 SAPI-support started with PHP 4.2.0. PHP 4.2.3 works with + Apache 2.0.39, don't use any other version of Apache with PHP 4.2.3. + However, the recommended setup is to use PHP 4.3.0 or later with the + most recent version of Apache2. + + All mentioned versions of PHP will work still with Apache 1.3.x. + + Warning + + Apache 2.0.x is designed to run on Windows NT 4.0, Windows 2000 or + Windows XP. At this time, support for Windows 9x is incomplete. Apache + 2.0.x is not expected to work on those platforms at this time. + + Download the most recent version of Apache 2.0.x and a fitting PHP + version. Follow the Manual Installation Steps and come back to go on + with the integration of PHP and Apache. + + There are two ways to set up PHP to work with Apache 2.0.x on Windows. + One is to use the CGI binary the other is to use the Apache module DLL. + In either case you need to edit your httpd.conf to configure Apache to + work with PHP and then restart the server. + + Note: Remember that when adding path values in the Apache + configuration files on Windows, all backslashes such as + c:\directory\file.ext must be converted to forward slashes, as + c:/directory/file.ext. A trailing slash may also be necessary for + directories. + __________________________________________________________________ + +Installing as a CGI binary + + You need to insert these three lines to your Apache httpd.conf + configuration file to set up the CGI binary: + + Example 2-5. PHP and Apache 2.0 as CGI +ScriptAlias /php/ "c:/php/" +AddType application/x-httpd-php .php + +# For PHP 4 +Action application/x-httpd-php "/php/php.exe" + +# For PHP 7 +Action application/x-httpd-php "/php/php-cgi.exe" + + Warning + + By using the CGI setup, your server is open to several possible + attacks. Please read our CGI security section to learn how to defend + yourself from those attacks. + __________________________________________________________________ + +Installing as an Apache module + + You need to insert these two lines to your Apache httpd.conf + configuration file to set up the PHP module for Apache 2.0: + + Example 2-6. PHP and Apache 2.0 as Module + +# For PHP 7 do something like this: +LoadModule php7_module "c:/php/php7apache2.dll" +AddType application/x-httpd-php .php + +# configure the path to php.ini +PHPIniDir "C:/php" + + Note: Remember to substitute your actual path to PHP for the c:/php/ + in the above examples. Take care to use either + php5apache2.dll in your LoadModule directive and not php5apache.dll + as the latter ones are designed to run with Apache 1.3.x. + + Note: If you want to use content negotiation, read related FAQ. + + Warning + + Don't mix up your installation with DLL files from different PHP + versions. You have the only choice to use the DLL's and extensions that + ship with your downloaded PHP version. + __________________________________________________________________ + +Sun, iPlanet and Netscape servers on Microsoft Windows + + This section contains notes and hints specific to Sun Java System Web + Server, Sun ONE Web Server, iPlanet and Netscape server installs of PHP + on Windows. + + From PHP 4.3.3 on you can use PHP scripts with the NSAPI module to + generate custom directory listings and error pages. Additional + functions for Apache compatibility are also available. For support in + current web servers read the note about subrequests. + __________________________________________________________________ + +CGI setup on Sun, iPlanet and Netscape servers + + To install PHP as a CGI handler, do the following: + + * Copy php7ts.dll to your systemroot (the directory where you + installed Windows) + * Make a file association from the command line. Type the following + two lines: + +assoc .php=PHPScript +ftype PHPScript=c:\php\php.exe %1 %* + + * In the Netscape Enterprise Administration Server create a dummy + shellcgi directory and remove it just after (this step creates 5 + important lines in obj.conf and allow the web server to handle + shellcgi scripts). + * In the Netscape Enterprise Administration Server create a new mime + type (Category: type, Content-Type: magnus-internal/shellcgi, File + Suffix:php). + * Do it for each web server instance you want PHP to run + + More details about setting up PHP as a CGI executable can be found + here: http://benoit.noss.free.fr/php/install-php.html + __________________________________________________________________ + +NSAPI setup on Sun, iPlanet and Netscape servers + + To install PHP with NSAPI, do the following: + + * Copy php7ts.dll to your systemroot (the directory where you + installed Windows) + * Make a file association from the command line. Type the following + two lines: + +assoc .php=PHPScript +ftype PHPScript=c:\php\php.exe %1 %* + + * In the Netscape Enterprise Administration Server create a new mime + type (Category: type, Content-Type: magnus-internal/x-httpd-php, + File Suffix: php). + * Edit magnus.conf (for servers >= 6) or obj.conf (for servers < 6) + and add the following: You should place the lines after mime types + init. + +Init fn="load-modules" funcs="php7_init,php7_execute,php7_auth_trans" shlib="c:/ +php/sapi/php7nsapi.dll" +Init fn="php7_init" LateInit="yes" errorString="Failed to initialise PHP!" [php_ +ini="c:/path/to/php.ini"] + + The php_ini parameter is optional but with it you + can place your php.ini in your web server configuration directory. + * Configure the default object in obj.conf (for virtual server + classes [Sun Web Server 6.0+] in their vserver.obj.conf): In the +