You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,12 @@
5
5
# Why?
6
6
7
7
[The official recommendation](https://help.jagex.com/hc/en-gb/articles/13413514881937-Downloading-the-Jagex-Launcher-on-Linux)
8
-
points to several community projects, most of which involve running the launcher in Wine or a similar environment. However, I really wanted a native solution, or one
8
+
points to several community projects, most of which involve running the launcher in Wine or a similar environment.
9
+
However, I really wanted a native solution, or one
9
10
that didn't require installing a 1.5GB compatibility layer solely for launcher functionality.
10
11
11
-
While there is a project that served as the inspiration for this one, and functions seamlessly on Linux, there were some boxes that it didn't tick for me:
12
+
While there is a project that served as the inspiration for this one, and functions seamlessly on Linux, there were some
13
+
boxes that it didn't tick for me:
12
14
13
15
- Its installation size is ~460MB
14
16
- Lack of support for overriding the client launch command/environment
@@ -18,7 +20,8 @@ In comparison, the linux-amd64 build for `golt` is a single 6.8MB binary.
18
20
19
21
# Installation
20
22
21
-
Either download the latest binary from the [Releases](https://github.com/chowder/golt/releases) page (or build it yourself), and add it to a directory on your `PATH`.
23
+
Either download the latest binary from the [Releases](https://github.com/chowder/golt/releases) page (or build it
24
+
yourself), and add it to a directory on your `PATH`.
22
25
23
26
Then, create a desktop entry for the application:
24
27
@@ -52,17 +55,18 @@ The login flow is currently done in the browser:
52
55
- The OAuth login redirects to a page which invokes a scheme handler
53
56
- The game login step redirects to `http://localhost`
54
57
55
-
These redirect URLs are validated server side, so cannot be modified on the client side.
58
+
These redirect URLs are validated server side, so cannot be modified on the client side.
56
59
57
-
As for the iptable entry, most Linux distros don't allow binding to port 80, so `golt` binds to port 8080 instead.
60
+
As for the iptable entry, most Linux distros don't allow binding to port 80, so `golt` binds to port 8080 instead.
|`GOLT_GAME_PATH`|`RuneLite.AppImage`| Either a binary on `PATH`, or an absolute path to the client to launch.<br/>This value is passed to `exec.Command`([docs](https://pkg.go.dev/os/exec#Command)) |
|`GOLT_GAME_PATH`|`RuneLite.AppImage`| Either a binary on `PATH`, or an absolute path to the client to launch.<br/>This value is passed to `exec.Command`([docs](https://pkg.go.dev/os/exec#Command)) |
69
+
|`GOLT_BIND_PORT`|`8080`| Local port to which `golt` will bind to to receive the OAuth response callback.<br/>If this is not `80`, you must set up an iptable entry to redirect inbound traffic from port `80` to this port. |
0 commit comments