- Installing VS Code
- Recommended VS Code Extensions
- Operating and pointing to WindowsOS >> goes to WSL (Default)
- We change the setting to go directly into the WSL through the extensions.
- Recommended VS Code Extensions
- This extension includes WSL Remote Development (Work 100% here)
- Remote - SSH - Work with source code in any location by opening folders on a remote machine/VM using SSH. Supports x86_64, ARMv7l (AArch32), and ARMv8l (AArch64) glibc-based Linux, Windows 10/Server (1803+), and macOS 10.14+ (Mojave) SSH hosts.
- Remote - Containers - Work with a separate toolchain or container based application by opening any folder mounted into or inside a container.
- Remote - WSL - Get a Linux-powered development experience from the comfort of Windows by opening any folder in the Windows Subsystem for Linux.
- This helps with skipping things and make things faster.
- https://code.visualstudio.com/docs/remote/wsl-tutorial (Tutorial)
After Installed the WSL remote development, it looks like
Now we can communicate with AWS EC2 or Docker easily without intervening and going over the Windows OS.
- Set up for WSL
- Using Linux >> download WSL
- Micro VM (Virtual Machine)
- It sits on top of Windows OS <-> Hardware
- Own Fire Storage
- It's slower to download in mnt rather than downloading WSL
- Solution: WSL >> We want to do our all codes in the root (not in mnt)
- This is faster and better
- We want to stay in WSL as much as possible
- Set up AWS
- AWS configure cd
'Basic Coding Info' 카테고리의 다른 글
swagger makes document for viewing it in a nice way (0) | 2022.07.28 |
---|---|
Yarn Basics (0) | 2022.06.14 |
If BitBucket Data shows different Snapshots.. (0) | 2022.04.28 |
What is Data Migration? (0) | 2022.04.28 |
[Visual Studio ShortKey] Useful Short Key (0) | 2022.04.19 |