Binhex GoLand

Binhex GoLand is a container-based, browser-accessible deployment of JetBrains GoLand, an integrated development environment for Go applications.

  • Development
  • Productivity
  • Tools & Utilities
Binhex GoLand is a container-based, browser-accessible deployment of JetBrains GoLand, an integrated development environment for Go applications. It runs GoLand in a Docker container so self-hosters can develop Go, JavaScript, TypeScript, Node.js, SQL, database, Docker, Kubernetes, and Terraform projects from a home server. It is useful for developers who want a full IDE without installing desktop software.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
72last commit 9 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 31 days ago

GitHub stars
1
Open issues
0
Last commit
2026-11-12
Latest release
2026.3-1-01
License
GPL-3.0
Activity
rising

Checked 9 days ago - source: GitHub (binhex/arch-goland)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the Soulseek listen port In the soulseek config, set listen_port to a free incoming port on your home server, such as 2234. Setting it to 0 disables incoming peer connections, which can stop other Soulseek users from connecting to you. source
  • Keep music in Artist/Album folders Seakarr expects finished music to be stored in Artist Name/Album Name folders, with the files inside the album folder. Keep that library path consistent, because moving or scattering these folders can confuse organization and make it harder to reuse downloaded files. source
  • Choose search mode explicitly When using command-line selectors like --artist/--album or --batch-file, add --mode manual or --mode batch if the configured mode is auto. These selector options do not silently override the configured mode, and the wrong mode can make Seakarr skip or fail the target. source
  • Access GoLand in a browser Set VNC_PASSWORD and publish ports 5900 and 6080 to open GoLand from a browser. source

Fetched 39 days ago - each note links to its source

Alternatives (6)

  • CodeBuddy - CodeBuddy is a self-hosted programming-assignment management system that lets instructors deliver coding exercises in programming courses a…
  • Lapce - Lightning-fast and Powerful Code Editor written in Rust.
  • VSCodium - VSCodium is a community-driven, freely-licensed binary distribution of Microsoft's VS Code.
  • Vim - Advanced text editor with multiple modes, syntax highlighting, word completion, plugin support, built-in help, command-line tools, cross-pl…
  • Visual Studio Code - Free, extensible code editor with Git integration, AI-driven IntelliCode, and 30,000+ extensions, supporting various languages like Python,…
  • Zed Editor - Blazing fast, collaborative code editor with real-time multi-user support, built-in Vim mode, language-aware syntax trees, integrated termi…

Checked 54 days ago - source: AlternativeTo

Common questions

Which ports should I expose to reach GoLand?

Expose 6080 for the noVNC web interface and 5900 for standard VNC client connections.

How can I install extra packages inside the container?

Set ENABLE_STARTUP_SCRIPTS=yes and place startup scripts in /config/home/scripts/ to install packages from the Arch Repository or AUR.

Which PUID and PGID values should I use?

Set PUID and PGID to the user ID and group ID of the account you want the container to run as, which you can find with id.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads