Use the in-browser terminal
Every running instance has a root shell you can open from the console in one click. You need no SSH client and no SSH key, so it is the fastest way in right after you deploy. For daily work, file copies and port forwarding, add your own SSH key later.
You need: a GPUwerk account and an instance with status running. Nothing to install.
1. Opening a session
- Open the instance in the console.
- In its Connect section, click Open terminal in browser.
Result: a terminal window opens in the page with a root prompt on your instance. Your persistent files go in /workspace. There is no key to generate, upload or paste.
If the button reports that the instance is not running, wait until its status is running (or start it) and click again.
2. How a session works
Each time you open the terminal, your browser generates a fresh key pair for that session only. The console adds the public half to the instance for this session, connects with it, and removes it when the session ends. You never see or handle the key. Closing the window ends the session; the next one gets a new key.
3. A note on security
The session key is handled by GPUwerk's servers, briefly. The private half of that single-use keypair is sent once, over TLS, to a short-lived server-side process that exists only to relay your terminal session. It is held in memory for the life of the session, never written to disk or to logs, and destroyed when the session ends or times out. Your own SSH key is different: GPUwerk never generates, receives or sees its private half. The full disclosure is in the Privacy Policy.
4. Session limits
A session ends after a period of inactivity or when it reaches its maximum length, whichever comes first (by default 30 minutes idle or 8 hours in total). Processes you started in the foreground stop with it. Run long jobs under tmux, screen or nohup so they survive a closed session.
If a session ends while you are working, click Open terminal in browser again.
5. Prefer native SSH?
With your own key, GPUwerk is not involved in the session at all, and you get scp, port forwarding and editor integrations. The SSH keys guide takes about two minutes, and you can add the key to a running instance without redeploying.