If you are browsing this webpage, you have the pre-requisites.
Scroll down, click the link next to "User Installer" (VSCodiumUserSetup-x64-1.###.#####.exe)
Run the executable
Accept the license agreement (MIT License)
The default installation folder for a user is %LOCALAPPDATAL\Programs\VSCodium
Start Menu Folder is named VSCodium
Enable "Create a desktop icon", "Register VSCodium as an editor" and "Add to PATH".
Click "Install"
Click "Finish"
The IDE launches.
See "Getting Started with VSCodium": https://github.com/VSCodium/vscodium/blob/master/docs/getting-started.md
Add some recommended extensions:
Go to View > Extensions
Use the search input to look for useful plugins. Examples: Prettier; select the one that is not deprecated and click Install, Trust Publisher and Install
Trust some Microsoft domains: aka.ms,
Restart VSCodium.
Open Remote - SSH (author: jeanp413)
Open Remote - WSL (author: jeanp413)
Install the "Open Remote - WSL" extension.
Start a new VSCodium window.
Click "Connect to..." or the "Open a Remote Window" icon (><) at the bottom left
Select Connect to WSL at the top.
Connection should establish and VSCodium re-open. The bottom-left will show ">< WSL: Debian".
Select "Open Folder..."
Browse to the folder containing code and .git repository and click OK.
A workspace view will be loaded in VSCodium.
Click "Yes I trust the authors".
Install the "Open Remote - SSH" extension.
Start a new VSCodium window.
Click "Connect to..." or the "Open a Remote Window" icon (><) at the bottom left.
Select Connect to Host...
Enter the user@hostname ; for a raw IPv6 address, see instructions for editing SSH configuration.
A new VSCodium window should open and establish a connection. The bottom-left will show ">< SSH: Hostname-or-IP".
Windows firewall may prompt you to allow connections back to VSCodium.
Select "Open Folder..."
Browse to the folder containing code and .git repository and click OK.
A workspace view will be loaded in VSCodium.
If this is your server, click "Yes I trust the authors".
Click "Connect to..."
Select Open SSH Configuration File...
Add a host reference and the connection details. Example:
Include pageant.conf
Host ConnectionName
Hostname [2001:db8:85a3::8a2e:370:7334]
User username
Port 22
Now after you select "Connect to Host..." you enter ConnectionName and press Enter.
This method solves errors like "Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006) ".
Open WSL terminal.
Your PATH includes the Windows folder for VSCodium, which contains the codium binary.
Start VSCodium at your project location: codium /srv/www
You will receive a security prompt: "Do you trust the authors of the files in this folder?" Click "Yes, I trust the authors". Let this be a reminder to at least read the AI code you generate 😅
It won't be able to move files to the recycle bin, like in a real Windows folder.
It also seems unhappy about the Git repository being owned by other user; click "Use unsafe repository", the folder, and continue. But even so, it's bad about tracking commits done independently from VSCodium. There are some propietary features in WSL that integrate with VSCode (official) and not VSCodium (unofficial).
Syntax highlighting!
Clicking the "Git tree icon" on the left for the Source Control sidebar.
When you don't have a repository in the current folder, you can clone a new one.
REPOSITORIES shows the repository information, and allows selection.
CHANGES lists the files which have changed since last commit.
Click on a file to see the differences; old in red on the left, new in green on the right.
After reviewing the changes, click "+" to list the file in "Staged changes". Now you show differences of "Unstanged changes" or "Staged changes".
When everything is ready, enter a commit message and click "Commit".
GRAPH shows the history of commits.
Left-click a commit to show the file list, and click on a file to see that commit's differences.
Right-click on a commit for more options, including "Create Branch..." and "Create Tag..."
Right-click an HTML file and "Open in Integrated Browser". It's loaded as a real webpage in VSCod(ium). Doesn't really work with remote WSL!
Use the "Remote Explorer" icon on the left side to see the WSL targets.
Select the target and click the "Connect in new Window" icon.
A new window launches that attempts to install a Linux VSCodium "remote" on WSL.
It will download from VSCodium github repository. As long as your WSL can reach github, which requires IPv4 😁
On a remote SSH or WSL connection, use the Terminal > New Terminal menu at the top; or click an existing "TERMINAL" at the bottom. A terminal logs in with the credentials used for the "remote".
Right-click items on the navigation bar, Move to, Secondary Sidebar; your extension or browser will appear on the right.
When you've got two projects with separate Git repositories, but you wanna see both of them in the same VSCodium.
File > Add Folder to Workspace...
Navigate to the second project folder and click Add
File > Save Workspace As...
Save as domain.xyz.code-workspace ; perhaps in it's own folder?
This was a little buggy; I had to click Reconnect. Also it was more crowded than I expected; later I used File > New Window.
Connect a terminal.
mkdir -p .vscode
vi .vscode/tasks.json
{
"version": "2.0.0",
"tasks": [
{
"label": "1. Stop Running ${workspaceFolderBasename}",
"type": "shell",
"command": "pkill -f '${workspaceFolderBasename} args' || true",
"problemMatcher": []
},
{
"label": "2. Backup Old ${workspaceFolderBasename}",
"type": "shell",
"command": "mkdir -p .backups && [ -f ${workspaceFolderBasename} ] && mv ${workspaceFolderBasename} .backups/${workspaceFolderBasename}_$(date +%Y%m%d_%H%M%S) || true",
"problemMatcher": []
},
{
"label": "3. Go Build",
"type": "shell",
"command": "go",
"args": [
"build",
"-o",
"${workspaceFolderBasename}"
],
"problemMatcher": ["$go"]
},
{
"label": "Go: Backup & Rebuild",
"dependsOrder": "sequence",
"dependsOn": [
"1. Stop Running ${workspaceFolderBasename}",
"2. Backup Old ${workspaceFolderBasename}",
"3. Go Build"
],
"group": {
"kind": "build",
"isDefault": true
},
"presentation": {
"reveal": "always",
"panel": "shared"
}
}
]
}
Use the Terminal menu > Run Build Task...
Close the terminal when build is finished.