Hosting on a Server
EDA runs are heavy: it is common to run Odatix on a powerful remote machine (a lab server or cluster node) while you work from a laptop. This page covers running jobs remotely, keeping them alive after you disconnect, and reaching Odatix Explorer over the network.
Table of Contents
Run jobs remotely and disconnect
Because runs are daemon-driven, you can start a detached session over SSH and log out — the jobs keep running:
odatix fmax --tool vivado -d -S nightly
odatix ls # confirm the session is running
exit # jobs continue in the daemon
Reconnect later and re-attach the monitor:
odatix monitor -S nightly
See Job Monitor & sessions for the full session model.
Access Odatix Explorer over the network
Explorer serves a web UI. There are two ways to reach it from your workstation.
Option A — SSH tunnel (recommended)
Keep Explorer bound to localhost on the server, and forward its port through SSH. This is secure by default and needs no firewall changes.
odatix-explorer --nobrowser --port 8052
ssh -N -L 8052:localhost:8052 user@server
Then open http://localhost:8052 in your local browser. For a step-by-step guide, see the SSH tutorial.
Option B — expose on the local network
If the server and your workstation share a trusted network, bind Explorer to the network interface:
odatix-explorer --network --port 8052
Then browse to http://<server-address>:8052 from your workstation.
--network exposes Explorer to every machine that can reach the server on that port. Only use it on a trusted network, and prefer the SSH tunnel otherwise.
Keeping a foreground process alive
If you run Explorer (or an attached monitor) in the foreground over SSH and want it to survive a disconnect, run it inside a terminal multiplexer such as tmux or screen:
tmux new -s odatix
odatix-explorer --network --port 8052
# detach with Ctrl-b then d; reattach later with: tmux attach -t odatix