Debugging-Why some people say you can develop segmentfault directly on the server

Why do some people say that PHP can be developed directly on the server?
I have been in the experience of the local development, upload the server process

Reply content:

Why do some people say that PHP can be developed directly on the server?
I have been in the experience of the local development, upload the server process

A lot of big companies are like this, server Linux, you have an account can board the server, but not directly, to first boarded the board, and then boarded the server through the board, in such cases, many people directly on the server with vim write.

Vim as the editor of God, configuration is still very useful.

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

Nothing to do, see the actual situation.

Most of the servers are Linux, and most of the Linux systems are not very good desktops, and few people use Linux as desktops. This leads to a lot of situations where the client and server are not the same environment, for some simple sites, rely on very little, just read and write the database, the operating system is not as much of a problem.

However, if the external dependencies of the site are many, such as the need to use some of the features of Linux, it is not easy to ensure that the development of the machine and server environment exactly the same, then directly on the server development and testing is simple.

But if a project needs more people to develop at the same time, on the server is not very good, because it is possible to overwrite the other changes, the best solution is to use virtual machines, such as Vagrant.

Because the code itself is to run on the server, ah, its own notebook environment and the server is so much worse, and then there may be a variety of peripheral needs to connect the tool system through windows are not connected.
And then upstairs talking about a few people together on a server development is actually no problem.
Because for the development environment, everyone can have their own apache+mysql, but the port is different. Then the code is versioned using Git, which can be sent to the test server for testing on a regular basis and then tagged with the version of the completed test. When upgrading, pick a stable version.
PS: To compile the language will not be written on their own computer ... If the environment is going to be a little bit too busy to die ...

• It can be written directly on the server, not directly in the production environment. It is usually written directly on it and will not be written to the user's version.
• With regard to PHP, the main PHP engine supports changes to see results immediately, whether interpreted or JIT-based.
• There are always some people think that with vim+ a variety of open source plug-ins than the IDE, in vim you refactor a variable to try, the VIM plug-in auto-completion and the IDE inside the baby, Vim is just a text editor.

Can be developed on the server .... scripting language

It is not a problem to ensure that it is operational and where it is developed.
There seems to be such a word. Where to write code doesn't matter, it's important where the code runs.

As long as you can enter the code can write it is not-just directly on the server write bad, generally still do not do so.

Writing PHP only requires an editor, where can not be developed?

In fact, this situation is quite a lot. For example, you just wrote an application a few days after a bug, you know how to change after the service will definitely get rid of it. For example, you go out to play, burst of inspiration want to write a shell, this time in the mobile end after writing to pass up, again suitable.

Say humorous digression.

It used to be system management.
Development environment is multi-person +php.

Of course not, like Wang Ziting, local tyrants company or something,

But if a project needs more people to develop at the same time, on the server is not very good, because it is possible to overwrite the other changes, the best solution is to use virtual machines, such as Vagrant.

Small project Small Place after all,
Locally, sometimes personal computer vmplayer (this thing is more conscience, do not set port forwarding and so on can be directly ssh and VNC in.) Someone will go in and use Vim, which is what the main topic says, to develop PHP directly on the server.

Second, sometimes open a server account umask and group ID, LDAP and other black technology, and then multi-account ssh into git commit.

Third, sometimes it is to use the SVN post-commit script and SVN export this black technology more than one person to submit multiple changes at the same time.

Of course, the development of the server, generally speaking is ssh+vim+git ...

It feels like this is the right thing to do, and then you understand that it's a good, efficient way to do it.

