This content originally appeared on DEV Community and was authored by L.M MinKing.
After recently vibe-ing code, I’ve encountered some server issues, including but not limited to deployment, locating Docker container errors, fixing server time zones, insufficient disk space, and other issues.
In the past, I had to log in through SSH and troubleshoot each one myself. For example, when my disk space was insufficient, I used to run df -h and then troubleshoot each one, ultimately discovering that the Docker cache and some unused images were taking up too much space. Now, using the cursor with appropriate prompts, you can have it log in directly to your server, perform these locating operations, and then help you clean up disk space. While this is great, I’ve also experienced setbacks. I saw the cursor execute the command “docker system prune -f,” which doesn’t delete running containers, but it executed some extra commands that caused them to be deleted. Fortunately, I had persisted the data, and this was my test environment.
So, we need to add some rules to the cursor to prevent the AI from executing seriously incorrect commands and causing losses.
But overall, I think the efficiency improvement is quite impressive.
It is indeed very cool when auto run is turned on, but we still need to take a closer look to prevent serious problems
This content originally appeared on DEV Community and was authored by L.M MinKing.