Porta On Prem Support Checklist

Note

References to XXX.XXX.XX.XXX means the current machine’s IPv4 address (usually under d3net in Powershell’s ipconfig output).

1. Docker
   • porta container is running
   • porta-db / porta-db-2 / porta-db-3 container is running
     • The container name will be machine dependent
   • porta-socket-server container is running
   • porta-redis container is running
   • There are no extra containers running
     • Containers, or container groups, prefixed with porta are expected.

     Caution

     Any strangely named containers using a portadisguise image will interfere with Porta and must be stopped and deleted. Then the porta container should be restarted.

2. Porta
   • Porta is being accessed by its IP address in the browser: http://XXX.XXX.XX.XXX:8080 (not localhost)
   • Under Settings > Integrations > Socket Server, the URL is http://XXX.XXX.XX.XXX:6001
   • When sending/saving a page —> the page in the playlist has a channel selected
   • In Porta’s menu under Window > Settings > Channels, the correct channels are listed
     • if not, use the sync button in the channel panel
   • In Porta’s menu under Window > Settings > Preference, “Enable Play Groups” and “Enable play group sequence” are enabled
   • In Porta’s menu under Window > Settings > Preference, “Local Live Preview” is set as desired
   • In Porta’s menu under Window > Settings > Integrations, the desired integrations are active and configured
     • Google OAuth and Ipsum server require additional configuration, double click to configure
3. Designer
   • Designer is currently running
   • The active project in Designer is the expected project for Porta’s selected page/template/channel
   • Is the Designer API docs “Try it out” working for /session/sockpuppet/patches?
4. Unreal
   • Unreal is currently running
   • Unreal plugins are up to date
   • The Unreal project is the expected project for Porta’s selected page/template/channel
   • The Unreal game is running
   • Project settings for Porta Plugin are referencing the correct Porta instance
     • ConnectionURL: http://XXX.XXX.XX.XXX:6001 or http://porta.server:6001
     • API URL: http://XXX.XXX.XX.XXX:8000 or http://porta.server:8000
   • If using porta.server in the project settings, the host file has been updated to include the IP address of the machine running Porta
5. Porta Bridge
   • The Bridge is currently running
   • Only a single instance of the Bridge is running
     • Check the system tray and task manager for multiple instances

     Caution

     If multiple instances are running, stop all instances and restart the Bridge.

   • The Bridge version is up to date
   • Bridge is connected to the correct instance of Porta and Designer
     • If the Bridge is installed on a PX, it should be connected to that PX’s instance of Porta
   • Bridge is connected to the correct instance of Designer
   • Bridge API URL is http://XXX.XXX.XX.XXX:8000
   • Bridge Socket Server URL is http://porta-socket.server:6001 or http://XXX.XXX.XX.XXX:6001
6. Database
   • Database status icon color is green
   • Database health dashboard (http://XXX.XXX.XX.XXX:8000/health) is showing all green