


This article mainly introduces the automatic detection of PHP code (git/svn integrated PHP_CodeSniffer), which has certain reference value. Now I share it with you. Friends in need can refer to it
Background
When the company is developing, every time the code is submitted regardless of svn or git, the code will be simply automatically detected. The code logic cannot be checked, but at least the overall coding format can be ensured to be consistent. This function is quite useful. I have always wanted to know how it is implemented. It was not until recently that I started to understand what this automatic detection is.
Research approach
Generally, the company’s doc document will record the specific implementation of a certain function of various systems, and there may be more than one document. In the company’s doc No relevant information could be found through various keyword searches on the document
I found colleagues in the corresponding department and asked how it was implemented. The colleague replied that it was PHP_CodeSniffer and informed the github link. And clearly informed: Documentation? impossible. Then I added, everything is available on the Internet
Finally, I read a few articles on Baidu/Google, and I almost understood the practice
Part
PHP_CodeSniffer installation Reference materials
pear install PHP_CodeSniffer
I directly used the pear method to install it, which is much simpler and more convenient. The extension library installed using pear is basically in the PHP installation directory by default, such as mine: /opt/php-7.1.9/lib/php/PHP/CodeSniffer. You can refer to your own installation directory.
Use PHP_CodeSniffer directly from the command line as follows:
phpcs test.php
Set the code specification format of PHP_CodeSniffer.
# /opt/php-7.1.9/lib/php/PHP/CodeSniffer/src/Standards # 这个目录下列出了所有可以设置的格式(PSR1,PSR2,PSR12,Zend,Squiz等) phpcs --config-set default_standard Zend
svn/git installation
I won’t go into the description here, because it took me some time to install it on the virtual machine, so I referred to the information on the Internet.
Integrate PHP_CodeSniffer into git/svn
Every time an svn project is deployed, there will be a corresponding configuration file, including a hooks folder, which contains pre-commit. In this Just add the phpcs command to the file.
The principle of git is the same, there is a folder with hooks, and pre-commit is included in it.
Difference: Our company's svn is automatically detected during the commit process, while git is detected during git push. I guess it would be best if automatic code detection is integrated into the server where the engineering code is located. The remote host is directly accessed when svn commits. However, when git commits, the code is saved in the local branch, and only when git push is performed, it is submitted to the remote host, so git is an automatic detection operation performed during git push.
Written at the end
By understanding the automatic detection of PHP code, I discovered many problems.
I didn’t take the initiative to think about the problem. At the beginning, I just wanted to look up information in the doc instead of thinking about how this function is implemented. When I couldn't find the information in the doc and went straight to my colleagues
, when I was working on business needs, I often forgot to continue learning and think about other things. For example, many Linux commands have been forgotten, and the extension library PHP_CodeSniffer is very good. I will study the specific implementation when I have time. Need to think about things often
Through this automatic code detection, I found that I don’t understand anything, including pear, PSR, svn/git, yum/apt-get, etc. Even though I have used it before, I did not study it in depth or make corresponding records, so I quickly forgot about it. If you read a little more, you will realize that you know too little.
Thanks for the several materials used in this process
The above is the entire content of this article. I hope it will be helpful to everyone's study. For more related content, please pay attention to the PHP Chinese website!
Related recommendations:
The above is the detailed content of PHP code automatic detection (git/svn integrates PHP_CodeSniffer). For more information, please follow other related articles on the PHP Chinese website!

Effective methods to prevent session fixed attacks include: 1. Regenerate the session ID after the user logs in; 2. Use a secure session ID generation algorithm; 3. Implement the session timeout mechanism; 4. Encrypt session data using HTTPS. These measures can ensure that the application is indestructible when facing session fixed attacks.

Implementing session-free authentication can be achieved by using JSONWebTokens (JWT), a token-based authentication system where all necessary information is stored in the token without server-side session storage. 1) Use JWT to generate and verify tokens, 2) Ensure that HTTPS is used to prevent tokens from being intercepted, 3) Securely store tokens on the client side, 4) Verify tokens on the server side to prevent tampering, 5) Implement token revocation mechanisms, such as using short-term access tokens and long-term refresh tokens.

The security risks of PHP sessions mainly include session hijacking, session fixation, session prediction and session poisoning. 1. Session hijacking can be prevented by using HTTPS and protecting cookies. 2. Session fixation can be avoided by regenerating the session ID before the user logs in. 3. Session prediction needs to ensure the randomness and unpredictability of session IDs. 4. Session poisoning can be prevented by verifying and filtering session data.

To destroy a PHP session, you need to start the session first, then clear the data and destroy the session file. 1. Use session_start() to start the session. 2. Use session_unset() to clear the session data. 3. Finally, use session_destroy() to destroy the session file to ensure data security and resource release.

How to change the default session saving path of PHP? It can be achieved through the following steps: use session_save_path('/var/www/sessions');session_start(); in PHP scripts to set the session saving path. Set session.save_path="/var/www/sessions" in the php.ini file to change the session saving path globally. Use Memcached or Redis to store session data, such as ini_set('session.save_handler','memcached'); ini_set(

TomodifydatainaPHPsession,startthesessionwithsession_start(),thenuse$_SESSIONtoset,modify,orremovevariables.1)Startthesession.2)Setormodifysessionvariablesusing$_SESSION.3)Removevariableswithunset().4)Clearallvariableswithsession_unset().5)Destroythe

Arrays can be stored in PHP sessions. 1. Start the session and use session_start(). 2. Create an array and store it in $_SESSION. 3. Retrieve the array through $_SESSION. 4. Optimize session data to improve performance.

PHP session garbage collection is triggered through a probability mechanism to clean up expired session data. 1) Set the trigger probability and session life cycle in the configuration file; 2) You can use cron tasks to optimize high-load applications; 3) You need to balance the garbage collection frequency and performance to avoid data loss.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

Atom editor mac version download
The most popular open source editor

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

Notepad++7.3.1
Easy-to-use and free code editor

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function
