コンテンツにスキップ

Migrating to a Virtual Machine - FAQ

このコンテンツはまだ日本語訳がありません。

This page answers the questions we hear most often about moving Porta On Prem from Windows Subsystem for Linux (WSL) to a virtual machine (VM).

Today, Porta On Prem runs on your PX using WSL and Docker Desktop. We are moving it to a dedicated Linux VM that runs Docker Engine. Porta itself does not change. The application, its features, and your daily workflows stay the same. Only the foundation underneath changes.

WSL and Docker Desktop are built for developing software, not for running it in production. On your PX, this causes real problems:

  • Updates depend on several software layers that each change on their own schedule, so an update can break.
  • WSL storage grows over time but does not release space, so it slowly fills your Windows system drive.
  • Routine tasks rely on scripts in a terminal, which are difficult for anyone who is not a developer.

The VM removes these problems. Porta runs inside one self-contained Linux environment that behaves the same way, whatever the Windows host around it does.

Will Porta look or work differently for our operators?

Section titled “Will Porta look or work differently for our operators?”

No. Porta is the same application, with the same interface and the same workflows. Your operators do not need to learn anything new to run shows.

No. Your media stays on your networked drive or Designer machines, where it is today. Media uploaded directly to Porta will be migrated along with its data.

Will we lose any of our Porta content, such as templates, playlists, or schedules?

Section titled “Will we lose any of our Porta content, such as templates, playlists, or schedules?”

No. The migration copies your current Porta data into the VM and checks it before the system goes live. We rehearse this with a copy of your own data first.

The migration happens in a planned maintenance window that we agree with you in advance.

What happens if something goes wrong during the migration?

Section titled “What happens if something goes wrong during the migration?”

We rehearse the full migration on a separate test system that copies your setup, before we touch your live system. The complete process must pass several times before we schedule your migration.

During the migration, we keep a tested way to return to your current setup. If anything is wrong, we go back to it.

Disguise prepares and performs the migration. The one setup step that still uses a script is normally done by Disguise before we hand the machine back to you.

You install, update, and manage Porta through Porta Manager, a web interface. Both technical and non-technical staff can use it. Common tasks are buttons on a dashboard, not scripts you run in a terminal.

No. Porta Manager is designed so that routine tasks do not need a terminal or any developer knowledge.

Porta Manager keeps a record of every install, update, and maintenance action, with step-by-step logs. If something fails, you can see which step failed and send us that detail. This helps us support you faster.

You add the new Porta release in Porta Manager and follow clear on-screen steps. The update runs in place, in a stable Linux environment. You can even close the browser and continue later from the same point.

Do we get a new VM image for every Porta update?

Section titled “Do we get a new VM image for every Porta update?”

No. The VM image is only for the first setup. After that, you update Porta in place. We do not send a new image for each update.

Can we get the latest fixes without moving to the VM?

Section titled “Can we get the latest fixes without moving to the VM?”

New Porta releases are built for the VM deployment, so moving to the VM is how you receive the latest fixes and new features. The application itself stays the same; only the way we build and deliver it has changed.

Will the disk keep filling up the way it does now?

Section titled “Will the disk keep filling up the way it does now?”

No. Porta’s storage no longer grows without limit the way WSL does today. Porta VM uses a separate virtual disk with a size you control, kept apart from your Windows system drive.

Porta backs up its own data automatically on a regular schedule as before. You can also make a backup at any time with one click, for example before a large change to a show. Within Porta Manager, each backup shows its date, size, and location.

Yes. You can restore Porta to an earlier backup in one click. Before it restores, Porta Manager first backs up the current state, so you do not lose your most recent data.

No. We build the Porta VM to a standard, portable format. Porta is no longer tied to one specific machine. You do not need this to run Porta today, but it gives you room to grow in the future.

We agree to a maintenance window with you and confirm the details of your setup beforehand. We will let you know if we need anything from your team before the migration.