Debugging-Why do some people say they can develop SegmentFault directly on the server?

Why do some people say they can develop php directly on the server? In terms of experience, I have finished local development. Why do some people say that php can be developed directly on the server?
In terms of experience, I have finished local development and uploaded the server process.

Reply content:

Why do some people say they can develop php directly on the server?
In terms of experience, I have finished local development and uploaded the server process.

Many big companies use the Linux server. If you have an account, you can log on to the server, but you cannot log on directly. You must first log on to the stepping stone and then log on to the server through the stepping stone, in this case, many people write it directly on the server using vim.

Vim, as the editor's God, is easy to configure.

Because PHP does not need to be compiled, it can be run directly.

There is nothing to do, depending on the actual situation.

Most servers are Linux systems, while most Linux systems do not have very good desktops. Few users use Linux as desktops. In many cases, the client and server are not in the same environment. For some simple websites, the dependency is very small. It is nothing more than reading and writing the database, and the operating system is not much different.

However, if the website has a lot of external dependencies, for example, some features on Linux are required, it is not easy to ensure that the development machines and server environments are the same, in this case, development and testing on the server is simpler.

However, if a project needs to be developed by multiple people at the same time, it will not be easy to do on the server, because it may overwrite other modifications. In this case, the best solution is to use virtual machines, such as Vagrant.

Because the Code itself is to run on the server, its own notebook environment is so much different from the server, and then there may be a variety of utilities that need to be connected through windows.
Then the several people mentioned above are working together on a server.
For the development environment, everyone can have their own apache + mysql, but the port is different. Then the Code uses git for version control. You can regularly send the code to the test server for testing and tag the version that has completed the test. Select a stable version during upgrade.
PS: the language to be compiled won't be written on your computer any more... if there is something wrong with the environment, it will be too busy...

• It can be written directly on the server. It is not equal to writing directly in the production environment. It is usually written directly on the server and will not be written to the version for the user.
• About PHP, the mainstream php engines Support modification and immediately see the results, whether it is interpreted or JIT type.
• Some people always think that using vim + open-source plug-ins is better than IDE. In vim, you should try to refactor a variable to automatically complete the vim plug-in and compare it with the IDE, vim is just a text editor.

It can be developed on the server ....... Script Language

It is not a problem where development is ensured to be running.
There seems to be such a sentence. Where to write the code is not important, but where to run the code.

If you can enter the code, you can write it, right? It's just that it's hard to write it directly on the server. This is generally not the case.

Writing php requires only one editor. Where can I not develop it?

In fact, this situation is quite a lot. For example, if a bug occurs in an application you just wrote a few days later, you must change it directly on the server after you know how to change it. For example, when you go out to play, you may want to write a shell for inspiration. At this time, after writing it on the mobile end, it would be a good choice.

Out of question.

We used to manage systems.
The development environment is multi-user + PHP.

Of course, unlike Prince ting, which is a local company,

However, if a project needs to be developed by multiple people at the same time, it will not be easy to do on the server, because it may overwrite other modifications. In this case, the best solution is to use virtual machines, such as Vagrant.

After all, small projects,
Based on the local materials, sometimes the VMplayer on the PC (this item is more conscientious, you do not need to set port forwarding and other such information can directly SSH and VNC .) Someone will use VIM to develop php directly on the server.

Second, sometimes a server account such as umask, group ID, and ldap will be opened, and multiple accounts will be added to the git for submission through ssh.

Third, sometimes it is the use of svn's post-commit script and svn export, which many people Submit and modify at the same time.

Of course, the development on the server is generally said to be SSH + VIM + git...

It seems that this is something you can do, and then you can understand it very efficiently.