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
The current RPTerminal shipped with the desktop application is non-functional. This is simply because the web-socket backend logic to handle the terminal sessions and spawning pseudo-terminals was handled by apps/apiNode.js code. This is currently not being shipped with the desktop app.
The current RPTerminal is accessible only on the web application at /rterm. I need to create a native websocket terminal handler in Rust to ship it with the cross-platform desktop application too.
To-Do
create a pty handler in Rust to handle terminal connections
setup a bi-lateral communication channel
execute the terminal commands as child-processes
Alternatives to writing a native rust-pty handler
Bundle Node.js with the Tauri App
To package Node.js with the Tauri app, I can use tools like pkg or nexe to bundle the Node.js runtime and the Express server into a single executable.
Use Node.js as a Dependency
If I prefer to ship Node.js alongside the Tauri app, I can include the Node.js runtime as part of the app distribution.
The current
RPTerminal
shipped with the desktop application is non-functional. This is simply because the web-socket backend logic to handle the terminal sessions and spawning pseudo-terminals was handled byapps/api
Node.js code. This is currently not being shipped with the desktop app.The current RPTerminal is accessible only on the web application at
/rterm
. I need to create a native websocket terminal handler in Rust to ship it with the cross-platform desktop application too.To-Do
Alternatives to writing a native rust-pty handler
To package Node.js with the Tauri app, I can use tools like pkg or nexe to bundle the Node.js runtime and the Express server into a single executable.
If I prefer to ship Node.js alongside the Tauri app, I can include the Node.js runtime as part of the app distribution.
Performance
Playlist
The text was updated successfully, but these errors were encountered: