On-prem connection
On-prem runs Scenaven on a machine you control. Your files stay on that machine, and you get the full tool set: uploads, filters, dataset info, Python, and amAIra.
This is a mode in the same signed-in viewer, not a separate site — see One address.
Why on-prem
This is how you use Scenaven on your own simulations today.
Hosted cloud is a preview on prepared examples. Conversion, filters, and Python need a server that stays up, and that hosted compute has an infrastructure cost. On-prem puts that work on hardware you already run, inside your network.
On-prem use is the basis for enabling the same workflows on hosted cloud. A Scenaven admin turns them on from that feedback.
Switch from the viewer
Stay on the Scenaven page you already have open. On-prem is a mode in that same viewer.
- Click Infrastructure (top right). The panel is titled Choose infra.
- Select On-prem.
- Open Self-hosted setup. That panel lists the Docker setup in order. Follow those steps on the machine that will run Scenaven. You need Docker there before the later steps can succeed.
When Docker setup from that panel is finished, stay in Choose infra with On-prem selected and complete the connect step the panel shows. Infrastructure then reads Connected and On-prem. Uploads, filters, Python, and amAIra in this viewer use that machine.
Choose Cloud in the same panel to switch back to the hosted preview.
What you need
- Docker on the machine that will run Scenaven
- A browser that can reach that machine, on your network or over a VPN
- Disk space for session files and examples
After it connects
Infrastructure should say Connected, with on-prem selected.
- Uploads show Local conversion at the bottom of the sidebar. The file stays on that machine.
- Examples works as it does in the cloud. Datasets are prepared the first time the stack starts.
- Open is available for your own
.vtk,.vtkhdf,.vtp, and.vtufiles.
Where the files live
Uploads stay on the machine running Scenaven. Back that machine up the way you back up other data there.
Troubleshooting
| What you see | What to try |
|---|---|
| The download in Choose infra fails | Sign in on the cloud home page first, or leave the viewer and open it again from the home page |
| Infrastructure stays disconnected | Docker setup in Self-hosted setup is not finished. Follow those steps again, then switch to On-prem |
| The connect step fails | This browser must be able to reach the machine where Docker is running. Finish the panel’s setup steps, then switch to On-prem again |
| An upload fails | Check free disk space on the server, then the server logs described in the kit README |