摘要:先來(lái)講講為啥子,要寫(xiě)這篇文章因?yàn)榉?wù)器操作系統(tǒng),軟件版本,以及需求,都千奇百怪。的模塊使用來(lái)解析正則表達(dá)式該庫(kù)提供了很多種壓縮和解壓縮的方式,使用對(duì)包的內(nèi)容進(jìn)行。
先來(lái)講講為啥子,要寫(xiě)這篇文章
因?yàn)榉?wù)器操作系統(tǒng),軟件版本,以及需求,都千奇百怪。網(wǎng)上有很多教程每一種都不一樣!而且按照上面傻瓜式復(fù)制粘貼操作完成安裝的也在少數(shù)(本人用了很多但是沒(méi)有一個(gè)傻瓜操作成功的) 基本上都是有些經(jīng)驗(yàn)的遇到安裝錯(cuò)誤之后自行解決了!,所以我這面綜合寫(xiě)一個(gè)文章(其實(shí)就是閑的)
閑話不多說(shuō),開(kāi)始第一波操作
??毋庸置疑,在服務(wù)器進(jìn)行一系列環(huán)境搭建之前,做好創(chuàng)建一個(gè)快照(就是系統(tǒng)的某一個(gè)時(shí)間點(diǎn)的所有備份,就跟照片一樣,時(shí)間定格某一個(gè)畫(huà)面),防止你的系統(tǒng)被你安裝的亂七八糟的!到時(shí)候不好刪,直接回滾磁盤(pán)來(lái)的方便!
云服務(wù)器( 栗子:阿里云 )
創(chuàng)建辦法:控制臺(tái)->云服務(wù)器->選中你的實(shí)例->本實(shí)例的磁盤(pán)->創(chuàng)建快照 (這里如果你還找不到的話,聽(tīng)我的話放棄IT吧孩子)
使用辦法:控制臺(tái)->云服務(wù)器->選中你的實(shí)例->本實(shí)例的快照->回滾磁盤(pán)(這時(shí)候你的所有配置什么的環(huán)境啊,也都回滾了)
獨(dú)立服務(wù)器
獨(dú)立服務(wù)器,就是指你自己有的硬件服務(wù)器(通俗來(lái)講就是,你能看到的實(shí)體的服務(wù)器)
這里不做推薦,因?yàn)槿绻銜?huì)搭建快照軟件的話,這篇文章對(duì)你提升也不大!散了吧
如果你不會(huì)但是想學(xué)習(xí)一下的話,想了解一下的話可以看一下下面的鏈接
《10種linux下磁盤(pán)快照方式恢復(fù)系統(tǒng)》
??安裝nginx 之前先確定好自己的服務(wù)器操作系統(tǒng)對(duì)應(yīng)相對(duì)應(yīng)的操作系統(tǒng)來(lái)做!
contos(本人用的是新的CentOS 7.4 64,其實(shí)個(gè)人感覺(jué)版本什么的安裝程序差別不大)
1)用root用戶 找到你的目錄文件夾(本人推薦用root用戶進(jìn)行安裝,不知道的 "cd ~")
2)開(kāi)始安裝依賴(yum不知道是什么命令的,自己百度科普一下yum rpm 編譯安裝)
gcc:nginx編譯依賴gcc環(huán)境
yum install -y gcc-c++
pcre:(Perl Compatible Regular Expressions)是一個(gè)Perl庫(kù),包括 perl 兼容的正則表達(dá)式庫(kù)。nginx的http模塊使用pcre來(lái)解析正則表達(dá)式.
yum install -y pcre pcre-devel
zlib:該庫(kù)提供了很多種壓縮和解壓縮的方式,nginx使用zlib對(duì)http包的內(nèi)容進(jìn)行g(shù)zip。
yum install -y zlib zlib-devel
openssl:一個(gè)強(qiáng)大的安全套接字層密碼庫(kù),囊括主要的密碼算法、常用的密鑰和證書(shū)封裝管理功能及SSL協(xié)議,并提供豐富的應(yīng)用程序供測(cè)試或其它目的使用。nginx不僅支持http協(xié)議,還支持https(即在ssl協(xié)議上傳輸http).
yum install -y openssl openssl-devel
3)下載安裝nginx(我這里是1.12的版本,大家可以自行選擇)
wget http://nginx.org/download/nginx-1.12.0.tar.gz 下載安裝包
tar -zxvf nginx-1.12.0.tar.gz 解壓安裝包
cd nginx-1.12.0 找到解壓
接下來(lái)是重點(diǎn)的部分
注:安裝之前需要手動(dòng)創(chuàng)建上面指定的nginx文件夾,即/var/temp、/var/temp/nginx、/var/run/nginx/文件夾,否則啟動(dòng)時(shí)報(bào)錯(cuò)(如果不知道怎么新建文件夾《Linux 學(xué)習(xí)之創(chuàng)建、刪除文件和文件夾命令》,或者用ftp創(chuàng)建也行)
(為什么要這么做,因?yàn)檫@個(gè)是在網(wǎng)絡(luò)上面比較好的一個(gè)安裝目錄,要不然就用yum安裝了,安裝之后別說(shuō)nginx配置文件在哪?網(wǎng)站根目錄在哪?如果不知道這些配置文件的用途 推薦你們看《Nginx編譯參數(shù)大全 configure參數(shù)中文詳解》)
./configure
--prefix=/usr/local/nginx
--pid-path=/var/run/nginx/nginx.pid
--lock-path=/var/lock/nginx.lock
--error-log-path=/var/log/nginx/error.log
--http-log-path=/var/log/nginx/access.log
--with-http_gzip_static_module
--http-client-body-temp-path=/var/temp/nginx/client
--http-proxy-temp-path=/var/temp/nginx/proxy
--http-fastcgi-temp-path=/var/temp/nginx/fastcgi
--http-uwsgi-temp-path=/var/temp/nginx/uwsgi
--http-scgi-temp-path=/var/temp/nginx/scgi 配置命令 (一起復(fù)制)
make && make install 編譯并且編譯安裝
這就基本上可以了使用了
cd /usr/local/nginx/sbin/ 找到執(zhí)行文件地方
./nginx 啟用nginx
若報(bào)錯(cuò):[emerg] open() "/var/run/nginx/nginx.pid" failed (2: No such file or directory)
需要查看下是不是在 /var/run 文件夾下不存在 nginx 文件夾,不存在則新建
ps -ef | grep nginx 我們可以看一下這個(gè)是否啟動(dòng)成功了
也就是證明你安裝成功了
啟動(dòng)成功后訪問(wèn)你的ip或者域名就能看到
想要停止就要
cd /usr/local/nginx/sbin && ./nginx -s stop 強(qiáng)行停止
cd /usr/local/nginx/sbin && ./nginx -s quit 完整停止(建議使用)
cd /usr/local/nginx/sbin && ./nginx -s quit && ./nginx 重啟
cd /usr/local/nginx/sbin && ./nginx -s reload 重新加載配置
但是這樣很麻煩,一般我們都會(huì)用shell做成服務(wù),如果你嫌麻煩那么可以看一下如何封裝成服務(wù)
service nginx restart 重啟
service nginx stop 停止
service nginx start 啟動(dòng)
這樣是不是很帥,請(qǐng)看后續(xù)教程《小白系列:如何將軟件裝成service》
寫(xiě)累了,未完待續(xù)---2018-08-11
3. 安裝PHP??開(kāi)始安裝php了
contos(本人用的是新的CentOS 7.4 64,其實(shí)個(gè)人感覺(jué)版本什么的安裝程序差別不大)
1)回到到你的目錄文件夾(不知道的 "cd ~")
2)開(kāi)始安裝一些常用的php庫(kù)
依次執(zhí)行以下命令(常用的庫(kù),如果有什么要用的沒(méi)有安裝的,等安裝完php后自己再獨(dú)立安裝也可以)
yum -y install libmcrypt-devel mhash-devel libxslt-devel libjpeg libjpeg-devel libpng libpng-devel freetype freetype-devel libxml2 libxml2-devel zlib zlib-devel glibc glibc-devel glib2 glib2-devel bzip2 bzip2-devel ncurses ncurses-devel curl curl-devel e2fsprogs e2fsprogs-devel krb5 krb5-devel libidn libidn-devel openssl openssl-devel
3)下載并安裝php(我這里是7.1.11的版本,大家可以自行選擇)
wget http://cn2.php.net/distributions/php-7.1.11.tar.gz 下載php官方安裝包(速度還是蠻快的說(shuō))
tar -zxvf php-7.1.11.tar.gz 解壓安裝包
cd php-7.1.11 找到解壓
開(kāi)始配置編譯參數(shù)
./configure
--prefix=/usr/local/php7
--with-config-file-path=/usr/local/php7/etc
--enable-fpm
--with-mcrypt
--enable-mbstring
--enable-pdo
--with-curl
--disable-debug
--disable-rpath
--enable-inline-optimization
--with-bz2
--with-zlib
--enable-sockets
--enable-sysvsem
--enable-sysvshm
--enable-pcntl
--enable-mbregex
--with-mhash
--enable-zip
--with-pcre-regex
--with-mysqli
--with-gd
--with-jpeg-dir
--with-freetype-dir
--enable-calendar 配置命令 (一起復(fù)制)
make && make install 編譯并且編譯安裝(那這個(gè)時(shí)間就比較長(zhǎng)了,我先去吃點(diǎn)東西~)
直接啟動(dòng)會(huì)報(bào)錯(cuò),先依次執(zhí)行下面命令,將默認(rèn)的配置文件變成真正的配置文件
cp /root/php-7.1.11/php.ini-production /usr/local/php7/etc/php.ini
cd /usr/local/php7/etc
cp php-fpm.conf.default php-fpm.conf
cd /usr/local/php7/etc/php-fpm.d
cp www.conf.default www.conf
需要查看下是不是在 /var/run 文件夾下不存在 php7文件夾,不存在則新建
使用vim命令對(duì)php-fpm.conf的內(nèi)容進(jìn)行如下修改
cd /usr/local/php7/etc 找到配置文件夾
vim php-fpm.conf 打開(kāi)后輸入i進(jìn)入編輯模式
pid = /run/php7/php-fpm.pid
(大概在17行左右,記住把前面的 ; 去掉,至于為什么在/run/php7/這,因?yàn)楸救讼矚g和nginx保持一致)
之后按esc,在之后按shift+: 輸入wq回車 (這文檔編輯 就不在這教大家了)
cd /usr/local/php7/sbin && ./php-fpm 啟動(dòng)
然后查看一下是否啟動(dòng)成功
圖上就表示啟動(dòng)成功了
關(guān)閉比較麻煩
kill 進(jìn)程id (注意關(guān)閉之前確認(rèn)這個(gè)ID一定要,別關(guān)錯(cuò)了,【假裝這里有一個(gè)苦笑的表情】)
那么php就安裝完了如果有人問(wèn)到,為什么我php -v啥的不好使呢,這個(gè)跟windows一樣,需要放在環(huán)境變量里面,這個(gè)和上個(gè)面的nginx都可以封裝成系統(tǒng)的service,以下mysql也是一樣!這樣啟動(dòng),和重啟,關(guān)閉啥的就很簡(jiǎn)單了!請(qǐng)看后續(xù)教程《小白系列:如何將軟件裝成service》
該午休了,未完待續(xù)---2018-09-11
午休結(jié)束了,現(xiàn)在開(kāi)始繼續(xù)---2018-09-18
4.好了接下來(lái)就是 nginx 和 php 怎么一起工作了the first one
都說(shuō)建立專用的用戶組來(lái)運(yùn)行php和nginx那么好 我們?nèi)ソ⒁粋€(gè)最常見(jiàn)到的www-data
groupadd www-data
useradd www-data -g www-data -s /sbin/nologin -M
然后還是修改配置文件the second one
找到nginx的站點(diǎn)目錄 /usr/local/nginx/html/
新建一個(gè)文件叫phpinfo.php內(nèi)容是
(此時(shí)如果要通過(guò)http://你的ip地址/phpinfo.php,他會(huì)默認(rèn)給你下載下來(lái)這個(gè)php文件)the thrid one
找到nginx的配置文件夾/usr/local/nginx/conf中的nginx.conf
編輯一下將其中的
第二行的#user nobody;
改成user www-data;
第九行的#pid logs/nginx.pid;
改成 pid /var/run/nginx/nginx.pid;
將中間的
#location ~ .php$ {
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
#}
改成這種
location ~ .php$ {
root html;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
}
the fourth one
找到nginx的配置文件夾/usr/local/php7/etc/php-fpm.d中的www.conf
將其中的23行24行
user = nobody
group = nobody
改為
user = www-data
group = www-data
the end
重啟一下php
然后重啟一下nginx
怎么重啟我上面有寫(xiě)。這里就不重復(fù)了
你在訪問(wèn)一下 就會(huì)發(fā)現(xiàn)http://你的ip地址/phpinfo.php 可以解析了
具體的文件我放在下面,大家可以對(duì)比一下
而且用戶組也都變了
截圖:
nginx.conf
user www-data; worker_processes 1; #error_log logs/error.log; #error_log logs/error.log notice; #error_log logs/error.log info; pid /var/run/nginx/nginx.pid; events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; #log_format main "$remote_addr - $remote_user [$time_local] "$request" " # "$status $body_bytes_sent "$http_referer" " # ""$http_user_agent" "$http_x_forwarded_for""; #access_log logs/access.log main; sendfile on; #tcp_nopush on; #keepalive_timeout 0; keepalive_timeout 65; #gzip on; server { listen 80; server_name localhost; #charset koi8-r; #access_log logs/host.access.log main; location / { root html; index index.html index.htm; } error_page 404 /404.html; # redirect server error pages to the static page /50x.html # error_page 500 502 503 504 /50x.html; location = /50x.html { root html; } # proxy the PHP scripts to Apache listening on 127.0.0.1:80 # #location ~ .php$ { # proxy_pass http://127.0.0.1; #} # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 # location ~ .php$ { root html; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include fastcgi_params; } # deny access to .htaccess files, if Apache"s document root # concurs with nginx"s one # #location ~ /.ht { # deny all; #} } # another virtual host using mix of IP-, name-, and port-based configuration # #server { # listen 8000; # listen somename:8080; # server_name somename alias another.alias; # location / { # root html; # index index.html index.htm; # } #} # HTTPS server # #server { # listen 443 ssl; # server_name localhost; # ssl_certificate cert.pem; # ssl_certificate_key cert.key; # ssl_session_cache shared:SSL:1m; # ssl_session_timeout 5m; # ssl_ciphers HIGH:!aNULL:!MD5; # ssl_prefer_server_ciphers on; # location / { # root html; # index index.html index.htm; # } #} }
www.conf
; Start a new pool named "www". ; the variable $pool can be used in any directive and will be replaced by the ; pool name ("www" here) [www] ; Per pool prefix ; It only applies on the following directives: ; - "access.log" ; - "slowlog" ; - "listen" (unixsocket) ; - "chroot" ; - "chdir" ; - "php_values" ; - "php_admin_values" ; When not set, the global prefix (or /usr/local/php7) applies instead. ; Note: This directive can also be relative to the global prefix. ; Default Value: none ;prefix = /path/to/pools/$pool ; Unix user/group of processes ; Note: The user is mandatory. If the group is not set, the default user"s group ; will be used. user = www-data group = www-data ; The address on which to accept FastCGI requests. ; Valid syntaxes are: ; "ip.add.re.ss:port" - to listen on a TCP socket to a specific IPv4 address on ; a specific port; ; "[ip:6:addr:ess]:port" - to listen on a TCP socket to a specific IPv6 address on ; a specific port; ; "port" - to listen on a TCP socket to all addresses ; (IPv6 and IPv4-mapped) on a specific port; ; "/path/to/unix/socket" - to listen on a unix socket. ; Note: This value is mandatory. listen = 127.0.0.1:9000 ; Set listen(2) backlog. ; Default Value: 511 (-1 on FreeBSD and OpenBSD) ;listen.backlog = 511 ; Set permissions for unix socket, if one is used. In Linux, read/write ; permissions must be set in order to allow connections from a web server. Many ; BSD-derived systems allow connections regardless of permissions. ; Default Values: user and group are set as the running user ; mode is set to 0660 ;listen.owner = nobody ;listen.group = nobody ;listen.mode = 0660 ; When POSIX Access Control Lists are supported you can set them using ; these options, value is a comma separated list of user/group names. ; When set, listen.owner and listen.group are ignored ;listen.acl_users = ;listen.acl_groups = ; List of addresses (IPv4/IPv6) of FastCGI clients which are allowed to connect. ; Equivalent to the FCGI_WEB_SERVER_ADDRS environment variable in the original ; PHP FCGI (5.2.2+). Makes sense only with a tcp listening socket. Each address ; must be separated by a comma. If this value is left blank, connections will be ; accepted from any ip address. ; Default Value: any ;listen.allowed_clients = 127.0.0.1 ; Specify the nice(2) priority to apply to the pool processes (only if set) ; The value can vary from -19 (highest priority) to 20 (lower priority) ; Note: - It will only work if the FPM master process is launched as root ; - The pool processes will inherit the master process priority ; unless it specified otherwise ; Default Value: no set ; process.priority = -19 ; Choose how the process manager will control the number of child processes. ; Possible Values: ; static - a fixed number (pm.max_children) of child processes; ; dynamic - the number of child processes are set dynamically based on the ; following directives. With this process management, there will be ; always at least 1 children. ; pm.max_children - the maximum number of children that can ; be alive at the same time. ; pm.start_servers - the number of children created on startup. ; pm.min_spare_servers - the minimum number of children in "idle" ; state (waiting to process). If the number ; of "idle" processes is less than this ; number then some children will be created. ; pm.max_spare_servers - the maximum number of children in "idle" ; state (waiting to process). If the number ; of "idle" processes is greater than this ; number then some children will be killed. ; ondemand - no children are created at startup. Children will be forked when ; new requests will connect. The following parameter are used: ; pm.max_children - the maximum number of children that ; can be alive at the same time. ; pm.process_idle_timeout - The number of seconds after which ; an idle process will be killed. ; Note: This value is mandatory. pm = dynamic ; The number of child processes to be created when pm is set to "static" and the ; maximum number of child processes when pm is set to "dynamic" or "ondemand". ; This value sets the limit on the number of simultaneous requests that will be ; served. Equivalent to the ApacheMaxClients directive with mpm_prefork. ; Equivalent to the PHP_FCGI_CHILDREN environment variable in the original PHP ; CGI. The below defaults are based on a server without much resources. Don"t ; forget to tweak pm.* to fit your needs. ; Note: Used when pm is set to "static", "dynamic" or "ondemand" ; Note: This value is mandatory. pm.max_children = 5 ; The number of child processes created on startup. ; Note: Used only when pm is set to "dynamic" ; Default Value: min_spare_servers + (max_spare_servers - min_spare_servers) / 2 pm.start_servers = 2 ; The desired minimum number of idle server processes. ; Note: Used only when pm is set to "dynamic" ; Note: Mandatory when pm is set to "dynamic" pm.min_spare_servers = 1 ; The desired maximum number of idle server processes. ; Note: Used only when pm is set to "dynamic" ; Note: Mandatory when pm is set to "dynamic" pm.max_spare_servers = 3 ; The number of seconds after which an idle process will be killed. ; Note: Used only when pm is set to "ondemand" ; Default Value: 10s ;pm.process_idle_timeout = 10s; ; The number of requests each child process should execute before respawning. ; This can be useful to work around memory leaks in 3rd party libraries. For ; endless request processing specify "0". Equivalent to PHP_FCGI_MAX_REQUESTS. ; Default Value: 0 ;pm.max_requests = 500 ; The URI to view the FPM status page. If this value is not set, no URI will be ; recognized as a status page. It shows the following informations: ; pool - the name of the pool; ; process manager - static, dynamic or ondemand; ; start time - the date and time FPM has started; ; start since - number of seconds since FPM has started; ; accepted conn - the number of request accepted by the pool; ; listen queue - the number of request in the queue of pending ; connections (see backlog in listen(2)); ; max listen queue - the maximum number of requests in the queue ; of pending connections since FPM has started; ; listen queue len - the size of the socket queue of pending connections; ; idle processes - the number of idle processes; ; active processes - the number of active processes; ; total processes - the number of idle + active processes; ; max active processes - the maximum number of active processes since FPM ; has started; ; max children reached - number of times, the process limit has been reached, ; when pm tries to start more children (works only for ; pm "dynamic" and "ondemand"); ; Value are updated in real time. ; Example output: ; pool: www ; process manager: static ; start time: 01/Jul/2011:17:53:49 +0200 ; start since: 62636 ; accepted conn: 190460 ; listen queue: 0 ; max listen queue: 1 ; listen queue len: 42 ; idle processes: 4 ; active processes: 11 ; total processes: 15 ; max active processes: 12 ; max children reached: 0 ; ; By default the status page output is formatted as text/plain. Passing either ; "html", "xml" or "json" in the query string will return the corresponding ; output syntax. Example: ; http://www.foo.bar/status ; http://www.foo.bar/status?json ; http://www.foo.bar/status?html ; http://www.foo.bar/status?xml ; ; By default the status page only outputs short status. Passing "full" in the ; query string will also return status for each pool process. ; Example: ; http://www.foo.bar/status?full ; http://www.foo.bar/status?json&full ; http://www.foo.bar/status?html&full ; http://www.foo.bar/status?xml&full ; The Full status returns for each process: ; pid - the PID of the process; ; state - the state of the process (Idle, Running, ...); ; start time - the date and time the process has started; ; start since - the number of seconds since the process has started; ; requests - the number of requests the process has served; ; request duration - the duration in μs of the requests; ; request method - the request method (GET, POST, ...); ; request URI - the request URI with the query string; ; content length - the content length of the request (only with POST); ; user - the user (PHP_AUTH_USER) (or "-" if not set); ; script - the main script called (or "-" if not set); ; last request cpu - the %cpu the last request consumed ; it"s always 0 if the process is not in Idle state ; because CPU calculation is done when the request ; processing has terminated; ; last request memory - the max amount of memory the last request consumed ; it"s always 0 if the process is not in Idle state ; because memory calculation is done when the request ; processing has terminated; ; If the process is in Idle state, then informations are related to the ; last request the process has served. Otherwise informations are related to ; the current request being served. ; Example output: ; ************************ ; pid: 31330 ; state: Running ; start time: 01/Jul/2011:17:53:49 +0200 ; start since: 63087 ; requests: 12808 ; request duration: 1250261 ; request method: GET ; request URI: /test_mem.php?N=10000 ; content length: 0 ; user: - ; script: /home/fat/web/docs/php/test_mem.php ; last request cpu: 0.00 ; last request memory: 0 ; ; Note: There is a real-time FPM status monitoring sample web page available ; It"s available in: /usr/local/php7/share/php/fpm/status.html ; ; Note: The value must start with a leading slash (/). The value can be ; anything, but it may not be a good idea to use the .php extension or it ; may conflict with a real PHP file. ; Default Value: not set ;pm.status_path = /status ; The ping URI to call the monitoring page of FPM. If this value is not set, no ; URI will be recognized as a ping page. This could be used to test from outside ; that FPM is alive and responding, or to ; - create a graph of FPM availability (rrd or such); ; - remove a server from a group if it is not responding (load balancing); ; - trigger alerts for the operating team (24/7). ; Note: The value must start with a leading slash (/). The value can be ; anything, but it may not be a good idea to use the .php extension or it ; may conflict with a real PHP file. ; Default Value: not set ;ping.path = /ping ; This directive may be used to customize the response of a ping request. The ; response is formatted as text/plain with a 200 response code. ; Default Value: pong ;ping.response = pong ; The access log file ; Default: not set ;access.log = log/$pool.access.log ; The access log format. ; The following syntax is allowed ; %%: the "%" character ; %C: %CPU used by the request ; it can accept the following format: ; - %{user}C for user CPU only ; - %{system}C for system CPU only ; - %{total}C for user + system CPU (default) ; %d: time taken to serve the request ; it can accept the following format: ; - %{seconds}d (default) ; - %{miliseconds}d ; - %{mili}d ; - %{microseconds}d ; - %{micro}d ; %e: an environment variable (same as $_ENV or $_SERVER) ; it must be associated with embraces to specify the name of the env ; variable. Some exemples: ; - server specifics like: %{REQUEST_METHOD}e or %{SERVER_PROTOCOL}e ; - HTTP headers like: %{HTTP_HOST}e or %{HTTP_USER_AGENT}e ; %f: script filename ; %l: content-length of the request (for POST request only) ; %m: request method ; %M: peak of memory allocated by PHP ; it can accept the following format: ; - %{bytes}M (default) ; - %{kilobytes}M ; - %{kilo}M ; - %{megabytes}M ; - %{mega}M ; %n: pool name ; %o: output header ; it must be associated with embraces to specify the name of the header: ; - %{Content-Type}o ; - %{X-Powered-By}o ; - %{Transfert-Encoding}o ; - .... ; %p: PID of the child that serviced the request ; %P: PID of the parent of the child that serviced the request ; %q: the query string ; %Q: the "?" character if query string exists ; %r: the request URI (without the query string, see %q and %Q) ; %R: remote IP address ; %s: status (response code) ; %t: server time the request was received ; it can accept a strftime(3) format: ; %d/%b/%Y:%H:%M:%S %z (default) ; The strftime(3) format must be encapsuled in a %{}t tag ; e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t ; %T: time the log has been written (the request has finished) ; it can accept a strftime(3) format: ; %d/%b/%Y:%H:%M:%S %z (default) ; The strftime(3) format must be encapsuled in a %{ }t tag ; e.g. for a ISO8601 formatted timestring, use: %{%Y-%m-%dT%H:%M:%S%z}t ; %u: remote user ; ; Default: "%R - %u %t "%m %r" %s" ;access.format = "%R - %u %t "%m %r%Q%q" %s %f %{mili}d %{kilo}M %C%%" ; The log file for slow requests ; Default Value: not set ; Note: slowlog is mandatory if request_slowlog_timeout is set ;slowlog = log/$pool.log.slow ; The timeout for serving a single request after which a PHP backtrace will be ; dumped to the "slowlog" file. A value of "0s" means "off". ; Available units: s(econds)(default), m(inutes), h(ours), or d(ays) ; Default Value: 0 ;request_slowlog_timeout = 0 ; The timeout for serving a single request after which the worker process will ; be killed. This option should be used when the "max_execution_time" ini option ; does not stop script execution for some reason. A value of "0" means "off". ; Available units: s(econds)(default), m(inutes), h(ours), or d(ays) ; Default Value: 0 ;request_terminate_timeout = 0 ; Set open file descriptor rlimit. ; Default Value: system defined value ;rlimit_files = 1024 ; Set max core size rlimit. ; Possible Values: "unlimited" or an integer greater or equal to 0 ; Default Value: system defined value ;rlimit_core = 0 ; Chroot to this directory at the start. This value must be defined as an ; absolute path. When this value is not set, chroot is not used. ; Note: you can prefix with "$prefix" to chroot to the pool prefix or one ; of its subdirectories. If the pool prefix is not set, the global prefix ; will be used instead. ; Note: chrooting is a great security feature and should be used whenever ; possible. However, all PHP paths will be relative to the chroot ; (error_log, sessions.save_path, ...). ; Default Value: not set ;chroot = ; Chdir to this directory at the start. ; Note: relative path can be used. ; Default Value: current directory or / when chroot ;chdir = /var/www ; Redirect worker stdout and stderr into main error log. If not set, stdout and ; stderr will be redirected to /dev/null according to FastCGI specs. ; Note: on highloaded environement, this can cause some delay in the page ; process time (several ms). ; Default Value: no ;catch_workers_output = yes ; Clear environment in FPM workers ; Prevents arbitrary environment variables from reaching FPM worker processes ; by clearing the environment in workers before env vars specified in this ; pool configuration are added. ; Setting to "no" will make all environment variables available to PHP code ; via getenv(), $_ENV and $_SERVER. ; Default Value: yes ;clear_env = no ; Limits the extensions of the main script FPM will allow to parse. This can ; prevent configuration mistakes on the web server side. You should only limit ; FPM to .php extensions to prevent malicious users to use other extensions to ; execute php code. ; Note: set an empty value to allow all extensions. ; Default Value: .php ;security.limit_extensions = .php .php3 .php4 .php5 .php7 ; Pass environment variables like LD_LIBRARY_PATH. All $VARIABLEs are taken from ; the current environment. ; Default Value: clean env ;env[HOSTNAME] = $HOSTNAME ;env[PATH] = /usr/local/bin:/usr/bin:/bin ;env[TMP] = /tmp ;env[TMPDIR] = /tmp ;env[TEMP] = /tmp ; Additional php.ini defines, specific to this pool of workers. These settings ; overwrite the values previously defined in the php.ini. The directives are the ; same as the PHP SAPI: ; php_value/php_flag - you can set classic ini defines which can ; be overwritten from PHP call "ini_set". ; php_admin_value/php_admin_flag - these directives won"t be overwritten by ; PHP call "ini_set" ; For php_*flag, valid values are on, off, 1, 0, true, false, yes or no. ; Defining "extension" will load the corresponding shared extension from ; extension_dir. Defining "disable_functions" or "disable_classes" will not ; overwrite previously defined php.ini values, but will append the new value ; instead. ; Note: path INI options can be relative and will be expanded with the prefix ; (pool, global or /usr/local/php7) ; Default Value: nothing is defined by default except the values in php.ini and ; specified at startup with the -d argument ;php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f www@my.domain.com ;php_flag[display_errors] = off ;php_admin_value[error_log] = /var/log/fpm-php.www.log ;php_admin_flag[log_errors] = on ;php_admin_value[memory_limit] = 32M
之后就剩mysql了,怎么還沒(méi)結(jié)束,我都寫(xiě)煩了(不知道大家有沒(méi)有看煩,私信我,我都會(huì)解答的)--2018-09-18
請(qǐng)大家給我一點(diǎn)寫(xiě)下去的勇氣!
文章版權(quán)歸作者所有,未經(jīng)允許請(qǐng)勿轉(zhuǎn)載,若此文章存在違規(guī)行為,您可以聯(lián)系管理員刪除。
轉(zhuǎn)載請(qǐng)注明本文地址:http://specialneedsforspecialkids.com/yun/40053.html
摘要:準(zhǔn)備工作服務(wù)器最好使用服務(wù)器,小白推薦安裝寶塔面板。備案域名小程序賬號(hào)建議注冊(cè)企業(yè)賬號(hào),可以使用已認(rèn)證的公眾號(hào)快速創(chuàng)建。七牛賬號(hào)使用,加快網(wǎng)站訪問(wèn)速度。如需使用小程序發(fā)帖,也會(huì)用到。注意不要使用以下的。 showImg(https://segmentfault.com/img/bVUUeU?w=600&h=280); 準(zhǔn)備工作 1服務(wù)器 最好使用Linux服務(wù)器,小白推薦安裝寶塔面板。...
摘要:原文地址作為一個(gè)天天造的人,必然要經(jīng)常訪問(wèn)谷歌等網(wǎng)站,所以前些日子買(mǎi)了自己搭了梯子。今天就跟大家分享一下,如何使用搭建個(gè)人博客。創(chuàng)建用戶,建立裸庫(kù),配置。 原文地址:https://www.xksblog.top/use-V... 作為一個(gè)天天造BUG的人,必然要經(jīng)常訪問(wèn)谷歌等網(wǎng)站,所以前些日子買(mǎi)了VPS自己搭了梯子。但如果只是用VPS來(lái)搭梯子那就太浪費(fèi)了,所以又折騰了一天,把自己之...
摘要:先來(lái)講講為啥子,要寫(xiě)這篇文章因?yàn)榉?wù)器操作系統(tǒng),軟件版本,以及需求,都千奇百怪。的模塊使用來(lái)解析正則表達(dá)式該庫(kù)提供了很多種壓縮和解壓縮的方式,使用對(duì)包的內(nèi)容進(jìn)行。 先來(lái)講講為啥子,要寫(xiě)這篇文章 因?yàn)榉?wù)器操作系統(tǒng),軟件版本,以及需求,都千奇百怪。網(wǎng)上有很多教程每一種都不一樣!而且按照上面傻瓜式復(fù)制粘貼操作完成安裝的也在少數(shù)(本人用了很多但是沒(méi)有一個(gè)傻瓜操作成功的) 基本上都是有些經(jīng)驗(yàn)的...
閱讀 1294·2021-10-08 10:05
閱讀 4107·2021-09-22 15:54
閱讀 3105·2021-08-27 16:18
閱讀 3107·2019-08-30 15:55
閱讀 1437·2019-08-29 12:54
閱讀 2748·2019-08-26 11:42
閱讀 543·2019-08-26 11:39
閱讀 2129·2019-08-26 10:11