Installation

Choose the fastest way to get Looksyk running

Looksyk supports multiple installation paths depending on your platform and workflow. If you want the lowest friction, use AUR on Arch or the AppImage on Linux. If you want remote access or mobile usage, choose Docker.

Platform overview

Arch Linux

  • AUR package: recommended
  • PKGBUILD: good if you want manual control

Linux desktop

  • AppImage: recommended for quick install
  • Manual build: supported
  • AppImage build from source: supported

Docker environments

  • Linux, Windows and macOS via Docker
  • Works well for browser and mobile access

Windows

  • The application is packaged in a portable (zip file) format.
  • Sync (with Git) has not been tested.
  • Community help is welcome for packaging and testing

macOS

  • Currently not a polished native install path
  • Community help is welcome for packaging and testing

Arch Linux / AUR

You can install Looksyk from the AUR. The package is called looksyk-desktop.

After installation, start Looksyk with looksyk.

Arch Linux / PKGBUILD

If you prefer building locally, run makepkg and install the package with pacman -U ./looksyk-desktop-<version>.tar.zst.

After installation, start Looksyk with looksyk.

Docker / Docker Compose

The repository contains two compose files:

Start Looksyk with docker compose up -d, then open http://localhost:11000 in Chrome or Chromium.

version: '3'
services:
  looksyk:
    image: sebastianrzk/looksyk
    ports:
      - "11000:11000"
    restart: unless-stopped
    volumes:
      - ./graph:/graph
      # SSH keys for accessing private repositories. Make sure to set correct permissions and ownership (root) on these files.
      #- ./my_id:/root/.ssh/id_rsa:ro
      #- ./known_hosts:/root/.ssh/known_hosts:ro
    # needed for accessing private repositories via SSH
    #network_mode: host

AppImage

Download the latest AppImage from the releases page.

chmod +x Looksyk-x86_64.AppImage
./Looksyk-x86_64.AppImage

AppImage manual build

  1. Build the components with bash build.sh. This builds frontend and backend and requires npm and cargo.
  2. Build the AppImage with bash build-appimage.sh.
  3. The AppImage will be created in the repository root.
  4. Make it executable and start it.
chmod +x Looksyk-x86_64.AppImage
./Looksyk-x86_64.AppImage

Production build / manual installation

  1. Run bash build.sh. This builds frontend and backend and requires npm and cargo.
  2. The application will be available in the target folder.
  3. Optional: create a desktop shortcut with sh create_desktop_shortcut.sh.
  4. Start the application with the created shortcut or by running ./application-wrapper/looksyk.
  5. You can change --port and --graph-location, and open Electron DevTools by passing --devtools true.
./application-wrapper/looksyk --port 11000 --graph-location ./graph

Windows

You can get Looksyk for Windows in two different ways:
  1. Pre-compiled binary from the releases page. Unzip the zip-file and run the start-looksyk.bat.
  2. Build it yourself (requires rust-toolchain, mingw-w64+libtool.dll, and nodejs + npm). Run the "build-windows.ps1" script to build the application, or start it with the development instructions

After installation

Multiple graphs and custom ports

You can run different Looksyk graphs at the same time by using different ports and graph locations. Use create_desktop_shortcut.sh or start the app manually with --port and --graph-location.

Need help?

If you have installation or setup problems, create an issue. If you want to improve the docs or add alternative installation methods, contribute via development and contribution.

FAQ / Troubleshooting

Known issues with building the application wrapper

Electron Forge is used to build the application wrapper. Sometimes it has incompatibilities with very new Node.js versions. If you encounter problems, try an older minor version of Node.js.

The application does not start / I get an error message

If the error says Address is already in use, another application is already using the configured port. This might be another Looksyk instance or any other program bound to the same port. You can change the port with the --port parameter.

Only one Looksyk backend should run on the same graph at a time. Running multiple Looksyk backends on the same graph can cause inconsistencies and data loss. Multiple frontends connected to one backend are fine, for example through browser sessions.