How to Set WSL as the Default Terminal on JetBrains IDEs (Webstorm, PyCharm, IntelliJ IDEA, PhpStorm, CLion, Rider, RubyMine)
This short tutorial explains the steps to set the WSL/WSL2 Terminal as your default terminal choice on any JetBrains IDE
- Linux 27
- AWS 17
- Node.js 15
- Ubuntu 15
- Debian 15
- RHEL 14
- Java 12
- CentOS 11
- JavaScript 7
- Docker 7
- PHP 6
- Testing 6
- System Design 6
- Git 5
- Lambda 5
- MySQL 4
- NPM 4
- AI 4
- HTTP 3
- Oracle DB 3
- Kubernetes 3
- Terraform 3
- APIs 2
- VirtualBox 2
- EC2 2
- MongoDB 2
- SSL Certificates 2
- Career 2
- Programming 2
- Springboot 2
- Databases 2
- NoSQL 2
- WebSockets 1
- SSH 1
- JDK 1
- SFTP 1
- OpenSSH 1
- SSH Keys 1
- Chroot 1
- UDP 1
- Rsyslog 1
- Syslog 1
- SUSE 1
- Angular 1
- Podman 1
- cURL 1
- Nano 1
- Vim 1
- Wget 1
- DynamoDB 1
- WSL 1
- TypeScript 1
- EKS 1
- LangChain 1
- OpenAI 1
- Grafana 1
- Prometheus 1
- Redis 1
- Caching 1
- MLOps 1
Recent posts
Testing JS & JSON Objects, Arrays, Object Arrays, Nested Objects, Sets, and Maps Using Chai.js
Comparing & testing JavaScript non-primitive/reference data types using the Chai library
12 Linux Commands Worth Remembering for Log File Operations (With Examples)
A tool list loved by sys admins and support engineers
[SOLVED] Fix npm ERR! code ELIFECYCLE, npm ERR! errno, npm ERR! Exit status, npm ERR! Failed at script, This is probably not a problem with npm issues during npm install, npm start, npm run build, or npm run script
Clean npm cache, node_modules, package-lock.json files to recover from all ‘npm ERR! code EINTEGRITY’ error messages during ‘npm install’
[SOLVED] Fix npm ERR! code EINTEGRITY, integrity checksum failed, tarball data seems to be corrupted, npm ERR! shasum check failed, npm WARN registry Unexpected warning issues during npm install
Clean npm cache, node_modules, package-lock.json files to recover from all ‘npm ERR! code EINTEGRITY’ error messages during ‘npm install’