[Cloud IDE] Experience

Cloud IDE experience

As a developer, in the general development workflow. We always build a local environment (including configuration of git, Ide, etc.). But this development environment only exists on one physical machine, and it is more troublesome if you want to synchronize this development environment on different machines (mobile phones, tablets, other PCs). We need to build the same development environment, and if there are changes in the environment, it will take time to adjust these changes.

One of my solutions before this was to develop directly on a cloud server, and use the remote development (Remote Development) extension plug-in of vscode to carry out corresponding development content. But such an operation is too much trouble, and the cost of the cloud server is too expensive and unrealistic.

Now CSDN has launched a cloud IDE to provide us with another choice. Of course, the function of cloud IDE is not the first of CSDN, but a very mature product. For specific usage methods of cloud IDE, you can check the documentation to understand it, so I won’t go into details here.

Cloud IDE product introduction
Cloud IDE usage tutorial
Free use address: Click [Cloud IDE] to start creating a workspace

basic use

After entering the cloud IDE, it is the familiar visual studio code interface. If you are not familiar with it, you can find articles to study by yourself.
Here I use the python environment for experience.

Another feature worth noting is that you can directly enter the cloud IDE by directly adding ide characters to the github repository. For example, https://github.com/Unity-Technologies/UnityCsReferencemodify it to https://idegithub.com/Unity-Technologies/UnityCsReference. If the network is not good, use the cloud IDE function directly and let the cloud IDE help you pull the code for easy viewing.

plug-in environment

After entering the cloud IDE, there is no obvious difference from the local vscdoe, and the basic Python extension plug-ins have been installed. There is no difference between debugging and running in the local environment, and the experience is very good.
Of course, this good experience disappeared when I restarted the working environment, because some commonly used plug-ins were not pre-installed in the cloud IDE. So I followed some plugins by myself, and these plugins were lost after restarting the workspace.

Development environment experience

After a simple experience

1. Only /ide/workspacethe contents under the directory will be saved
2. Since it is in the Ubuntu environment, you can use apt-get installthe command to install the software, and it will be lost after restarting.
3. For python development, use pip to install dependencies. Unsurprisingly, after restarting, it will be installed again. In addition, an error occurred:
   5. Write a simple server in python. Run the code cloud IDE to automatically discover a new port, which can be accessed directly in the browser. praise.
   
   

question

The command prompt in the Linux environment is too long

The first file encountered is the problem that the command prompt is too long. Here, the host name is too long, and it is estimated to be an automatically generated host name.

You can use vim ~/.bashrcthe command to remove the display of the host name in the file (the part in the red box in the figure below). Then use source ~/.bashrcApply to modify.

But unfortunately, this modification will become invalid when the workspace is closed. It is strongly recommended to provide methods to customize.
Another point of confusion is that if I use an empty project (do not fill in the git address), the terminal will display it in a different way.

configuration display problem

I don’t know if it’s a bug, but the specification configuration of the workspace is 2CPU4GB (just this one), but the configuration seen in htop is as follows: Then I
operated for less than 3 hours (only one workspace can be opened, open the new one and the old one) will be turned off) and tell me that it consumes 208 cores, but I don’t know how it is consumed.

Summarize

The current experience is basically consistent with the development experience of using cloud IDE and local IDE. But as the introduction said, Cloud IDE is a low-code development product for developers. Therefore, it is better not to be boring for medium-to-severe development.

The current recommendations for cloud IDEs are as follows:

1. Provides a mechanism for saving environment modifications, so that the environment (including the bash environment, pip downloaded packages, and VScode plug-ins) does not need to be reconfigured every time the workspace is restarted.
2. I hope that the dotnet environment can be arranged, this is quite common.