Linux installation

Installation

VSCode-Anywhere has been tested with several Linux distributions but it is impossible to test with all.

If you have any problems, please open an issue.

Installation example:

$ bash <(curl -sL https://raw.githubusercontent.com/gigi206/VSCode-Anywhere/V2/VSCode-Anywhere.sh) --help
usage :
  -h | --help        : print this help
  -e | --gitenv      : git branch (default: master)
  -d | --installdir  : installation directory (default: ~/VSCode-Anywhere)
  -v | --saltversion : saltstack version to use
  -p | --profile     : VSCode-Anywhere profile to use (default: linux_user)
  -s | --saltopts    : Salt options
$ bash <(curl -sL https://raw.githubusercontent.com/gigi206/VSCode-Anywhere/V2/VSCode-Anywhere.sh) --installdir <install_dir>

Replace <install_dir> by your installation path.

Options

Installation options are:

• gitenv (optional): git branch to use for installation (V2 by default)

• installdir (optional): installation directory (~/VSCode-Anywhere by default)

• saltversion (optional): Saltstack version to use (value evolves with time). It is not recommended to change this value (only for testing purposes for developers).

• profile (optional): type of installation profile (linux_user by default)

Profiles

There are 3 kinds of profile for different use cases :

• linux_admin: require administrator rights (for local use)

• linux_user: no administrator rights required (for local use)

• linux_portable: does not exist. Use linux_user instead (also works with a portable device like an usb stick)

profile	advantages	disadvantages
linux_admin	No Linux namespaces Better compatibility	/nix and /home/linuxbrew will be created on your system Not recommended if you already nix or brew is installed on your system Need to have a privileged account (sudo)
linux_user	No privileged account needed for the installation process and modules ‘’/nix’’ and /home/linuxbrew is encapsulated in the installdir directory with the namespaces	less compatibility Must have a Linux distribution that manages namespaces
linux_portable	Not needed at this time	Not needed at this time

Post-installation

Linux shortcuts icons

For some security reasons, some file managers like the gnome Files are no longer allowed to run desktop files inside the file manager which causes some problems for VSCode-Anywhere.

If you are in this case, there are multiple choices:

• if you are root, you can install another file manager that allow to run desktop files like nemo and run the desktop files with this manager

• On gnome, you can copy desktop files in the desktop and right-click on them and select Allow Launching

• Copy manually desktop files in ~/.local/share/applications or set install_desktop_files to True in vscode-anywhere.sls and runthe install.sh script:

vscode-anywhere:
  config:
    linux:
      install_desktop_files: True

HOME

After the installation with the linux_user profile (default), the home directory is no longer your home inside VSCode-Anywhere but it is insideVSCode-Anywhere/apps/vscode-anywhere/home.

This mechanism aims to avoid polluting your home directory. If you want to retrieve your real home directory, there are 2 ways:

• remove the VSCode-Anywhere/apps/vscode-anywhere/home and create a link that points to your home:

rm -fr VSCode-Anywhere/apps/vscode-anywhere/home
ln -s ~ VSCode-Anywhere/apps/vscode-anywhere/home

• override settings in vscode-anywhere.sls:

vscode-anywhere:
    env_core:
        USER: myuser
        HOME: myhome

Replace myuser and myhome by your real user and your real home directory.