Although Virtualenv is available on both Linux and Windows, there are some differences that you may find useful to understand.
Is there a difference to creating virtualenvs?
No, creating virtualenvs in Windows and Linux is exactly the same.
Can I use the same venv folder on both systems?
No. You will need to create 2 separate virtual environments. I suggest creating folders named winvenv and linvenv to tell them apart. You will have access to the same packages through pip, although you will need to use pip freeze if you wanted to replicate the packages exactly.
Do I activate the venvs in the same way?
No, but you CAN activate, and the differences are subtle. After creating the virtualenv, follow these steps:
Navigate to Scripts within the venv root. Type activate to use your venv in the current prompt
$ source linvenv/bin/activate
In the terminal, type source followed by the path to /bin/activate within the viretualenv folder
Have you spent the past several hours frantically searching the web for a solution of integrating Git with VSCode? Are you tempted to remove passphrases from your SSH Key just to get around Permission denied (publickey) errors every time you try and clone a repo?
Yes, it is disappointing that there is no clear documentation for this. Hopefully, this will fill the gap.
Windows 10 Git installed VSCode installed Created an SSH key using the Git terminal and is passphrase protected. Added your SSH public key to your chosen Git Service.
Before starting VSCode, open up a new Windows CMD window. Enter the command: start-ssh-agent and you will be prompted to provide the passphrase to your SSH Key.
Now you will be able to open VSCode and clone into your repository.
If you wanted to automate start-ssh-agent and open VSCode at the same time, I have built a batch script that will do just this.
Open text editor and paste in the code below. Save file as VSCode_ssh-agent.bat
I decided to place this file in my Windows home directory. On the Desktop, I created a shortcut to the .bat file and set the icon to point to:
C:\Users\[USER]\AppData\Local\Programs\Microsoft VS Code\Code.exe
The final result:
Check if SSH-AGENT is running. If not, start SSH-AGENT and ask for the passphrase for your key.
I have spent many an hour trying to figure out why VirtualBox 6 has given me terrible graphical performance on Linux Guests. I’m going to give you a no-mess solution that just might save your sanity.
Within the Settings for Your Virtual Machine, navigate to the Display > Screen tab. Under the Graphics Controller dropdown, select VMSVGA for your Linux guest.
Next, you will need to boot into the virtual machine and reinstall the VBOX Guest Additions for this to work (and cement it in with the obligatory reboot)
So you may be wondering why or when you might need to use this guide? You may have upgraded to VB6 from VB5 or earlier and trying to use a pre-existing VM. You may have installed VB6 for the first time, created and installed a new Linux guest VM and experienced graphical slowness. You may have tried (mostly) every setting within VBOX and viewed every forum post on the internet regarding VB performance issues and have got no further.
Admittedly, I was incredibly close to giving up altogether with VBOX 6 and going back to VBOX 5 as I have been struggling with this since VBOX 6 release. Finally, I have my VM back =)
If you ever wanted check if your login email/username credentials have ever been hacked or breached, you might be in luck! (or unluck in some cases…)
haveibeenpwned.com is a website that will check against known data-breaches from many major websites, or “pastes” from hackers who have compromised data and pasted the credentials publicly. It will also notify you about the type of data that has been leaked, which is important to know.
By now, people should be using the approach of using a strong, unique password for every different account / service that they sign up for, but more often then not, this is not the case.
If you don’t follow these practices, it might be time to start thinking about it; otherwise 1 databreach can quickly lead to many.
I like having my desktop filled with shortcuts to programs that I regularly use. In Ubuntu 18.04, there is a lack of a “right click > add shortcut to desktop” option. If you are missing this option too, don’t fret! There is another way to do just that.
In the Terminal, navigate to:
If you list all files with ls, you will see many different .desktop files each of which houses the information for executing a program. It also tells the UI where to find the icon that it should display.
Find the program that you wish to add to the desktop (you should find it here if it is installed through apt and it is a GUI application)
Copy the .desktop file to your own Desktop folder: