Download to read offline
Uploaded byBaruch Odem
VSCode Remote Extensions Development Pack
The document discusses options for working in a Linux environment on a Windows machine, highlighting remote SSH and WSL as effective solutions. It emphasizes the ability to connect to remote servers and use development containers hosted in the cloud, making the environment less dependent on local machines. Additionally, it mentions potential challenges with VPN connections and provides links for further assistance.
VSCode Remote Extensions Development Pack
- 1.
- 2. Are you dreamingabout A Linux Environment on your Windows machine?
- 3. Baruch Odem Team17 Developer(SAST) @baruchiro
- 4. Our options How towork in a Linux environment? How to do it locally without a VM? How to share development environment that is already configured? Bonus: How to connect to your environment from any device (including a Tablet!)
- 6. Remote SSH • Canconnect to a remote VM • Can connect to a Server Machine (without a UI) • Can replace other SSH interfaces
- 7. Remote WSL • Locallyand integrated with your Windows. • Shares the local network and resources. • (Problems when connecting via CheckPoint VPN) https://github.com/microsoft/WSL/issues/4246
- 8.
- 9. Correlation Engine POC SystemDependencies: • Go tooling • OPA • Graphiz Services: • Postgress IDE: • Extensions • Extensions Settings • Filesystem adjustments
- 10. Configre the extensionwith the service configurations Essential extensions
- 11. Host your devcontainer onthe cloud Bonus!
- 13. Summary REMOTE SSH REMOTEWSL REMOTE CONTAINERS Your environment is not dependent on a local machine anymore
- 14. Thank You! Share yourIDE with us
Editor's Notes
- #3 Our Objective: How to use the VSCode Remote extensions to develop on whatever OS we want. Take home: Your development is independent with your local machine.
- #11 There are templates, you don’t always need a docker-compose, and even no edit the Dockerfile
- #14 Obviously, remote development will require a stable internet connection, and sometimes you need close access to the running machine. Call to Action: If you have workspace dependencies, consider publishing your dev env with your source code. WIIFT: Use the right development environment for you.