Jump to content

PG3 to PG3x migration


Recommended Posts

Hello everyone,

PG3 is now in end of life. This means that there will be no more enhancements or fixes to it. This also means that as PG3x evolves, you will see more and more plugins (node servers) that will start to work on PG3x, but not PG3.

 

I am using a Polisy, do I need to upgrade?

Polisy came preinstalled with PG3, but can be upgraded to PG3x. 

We encourage you to migrate to PG3x, as this will allow you to stay current and use all of the plugins available. All the plugins working on PG3 also work on PG3x as PG3x is backward compatible.

PG3x is also using a different architecture which allows the platform to be more secure.

If you are unsure if you are already running PG3x or not:

  • If you are doing an "upgrade packages", but the version does not upgrade beyond 3.1.23, this means you are on PG3 (PG3x current release is 3.2.8)
  • Go to https://polisy.local:3000. If you see "Polyglot 3x" on the top left, you are on PG3x.
     

I am using an eisy, do I need to upgrade?

If you are using an eisy, it comes pre-installed with PG3x. Therefore, all you have to do to stay current is use the admin console or portal to "upgrade packages", which will update your PG3x version and other eisy components.
 

Upgrading to PG3x

  • First upgrade packages in admin console.
  • Enable PG3x by clicking this link: https://polisy.local:8443/rest/pg3x.enable
  • Reboot and wait for a beep, then a second beep.
    • Migrating node servers from PG3 to PG3x might take up to 2 minutes per node server. So, please be patient
  • Once all node servers show connected, reboot again.

NOTE: This process will remove PG2 and PG3. Furthermore, there is no "undo" for this process. Please make sure you take a backup first.

  • Thanks 1
Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...