What does "proficient use of Nginx" mean?

Question

2015/7/17
Description: I often see vague (large and comprehensive) descriptions such as "Proficient in using Nginx" in some job postings. I feel a little confused about such descriptions. Everyone's "proficiency standards" should be different, but still There are some similarities. I wonder how Juju people understand the "big problem" of "proficiently using (mastering) Nginx"?
(Proficient in its source code? Proficient in its configuration? Still?)

phpcn_u1582 · Answer

The key is that 使用, the use of tools like nginx refers to configuration, such as reverse proxy.

Generally speaking, you just want to ask about the details of the configuration. In fact, just know some commonly used ones, and others. Just check the documentation when you need them. But if it is an operation and maintenance position, the requirements will be higher.

If you are familiar with the source code and can write plug-ins, it can only be said that your worth will be much higher.

为情所困 · Answer

Just use it, let me tell you clearly that no company needs to modify nginx, except bat, such as Taobao's tengineer

PHP中文网 · Answer

To tell you the real reason, the JDs recruited are usually written by HR, or HR asks for it from the technical director.

1. If it is written by HR, HR themselves do not understand these things, they are just writing nonsense
2. If it is written by a technical leader, it must be because he does not know how to describe these things and can only write a general concept without being able to grasp these things.

If you want to hire a WEB programmer, you only need to be able to use the basic configuration. For operation and maintenance, the requirements will be much higher. Knowing the source code and writing plug-ins are basically not used in China except for the operation and maintenance development of some large companies. (It’s definitely good to know the source code yourself, but I’m only talking about recruitment here)

淡淡烟草味 · Answer

The main thing is installation and configuration. For example, building a service like Nginx+PHP-FPM, or Nginx+Tomcat, some commonly used configurations such as reverse proxy, rewrite rules, dynamic and static separation, load balancing, failover, etc.