MALT-WEBVIEW(1)
πΈ MALT-WEBVIEW(1) β the malt-webview girlie manual πΈ
okok so malt-webview is a thing you're gonna want to know about β it's the webserver situation for the MALT web GUI β¨ full title and all: MALT-WEBVIEW(1), from the General Commands Manual, and honestly it's giving essential. let's get into it π
π NAME π
malt-webview β the webserver for the MALT web GUI, no cap π¦
π«Ά SYNOPSIS π«Ά
malt-webview OPTIONS {malt-profile.json}
β¨ DESCRIPTION β¨
so the MALT web GUI is literally hosted by a nodeJS script, and that script is managed by the malt-webview command, periodt. by default it opens a socket listening on localhost and port 8080, so you can reach it at http://localhost:8080 π
π OPTIONS π
okay bestie here's the full menu, every single one, don't skip:
-n,'--no-auth'β turns off using HTTP authentification to secure the pages of the GUI. β οΈ and I need you to hear me on this one: caution, every user connected on the machine can access the GUI, and therefore your code. so likeβ¦ be careful, fr fr π-o,--overrideβ okay so if you copy a profile file from a remote machine onto your local one, your code might be stored somewhere else (different user, different path, you know the vibe π). override lets you alias some paths so it stays transparent to the GUI and you can still find your source code. the format issrc_path1:dest_path1,src_path2,dest_path2. the easiest use is to override the root directory of your project πp,--portβ forces it to use a different port than the default8080β¨versionβ displays the current version of MALT you're using π·οΈ-H,--hostβ lets you provide the host to listen on, if you don't want the default one (localhost) π-h,--helpβ displays a short help message summarizing the available options π«Ά
π ENVIRONMENT π
MALT_NODEJSβ you can set this to tell it which nodeJS to use, if the script cannot find it by itself π§
π REMOTE USAGE THROUGH SSH π
on clusters you might be interested in launching malt-webview remotely and forwarding it through ssh so you get it on your local machine β iconic, honestly. you can achieve this port redirection with ssh options:
ssh {YOUR_HOST} -L 8080:localhost:8080
where the first 8080 is the local port and the second one is the remote one β
π₯ AVOID EXPOSING THE REMOTE PORT π₯
when you're working remotely, you can avoid exposing the malt webview port publicly to the other users of the cluster by using a unix socket file in place of the port π«Ά
# remote malt-webview -p /home/myuser/malt.sock malt-PROFILE.json # on
your workstation ssh -L 8080:/home/myuser/malt.sock user@ssh-server
π VERSION π
this is the manpage of MALT version 1.4.1 π
πΈ SEE ALSO πΈ
malt-passwd(1), malt(1) β go read those too, iykyk π
okay that's the whole thing bestie, you're officially educated ππ
and for the little sign-off: this iconic page came from MALT-WEBVIEW(1) and it's dated October 2025 β go slay your web GUI, periodt π¦β¨
π¦ where this page comes from
- nixos 26.05: malt 1.4.1
- nixpkgs unstable: malt 1.4.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms