Update devcontainer configuration, PostgreSQL setup, and GWT user agent

.devcontainer/devcontainer.json

@@ -1,3 +1,21 @@
+/*
+This file contains the configuration options for the development container.
+
+The ulimit is needed because of https://pagure.io/python-daemon/issue/40
+
+Ports (https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/):
+- 8080:8080 - HTTP
+- 8443:8443 - HTTPS
+- 8787:8787 - Debug
+- 54323:54323 - VDSM
+- 9696:9696 - External network provider for OVN
+- 6642:6642 - Open Virtual Network (OVN) database
+- 35357:35357 - Keystone
+- 2222:2222 - VDSM SSH
+- 6100:6100 - noVCN
+- 7410:7410 - Kdump
+*/
+
 {
   "name": "oVirt",
   "build": {

DEVELOPMENT.adoc

@@ -1,8 +1,8 @@
 # oVirt Engine - Dev Container setup & building
 
-Before beginning, ensure that [Docker](https://www.docker.com/) is installed on the machine that the Dev Container will be running on. This could be your local device or on a [remote machine](https://code.visualstudio.com/docs/devcontainers/containers#_open-a-folder-on-a-remote-ssh-host-in-a-container).
+Before starting, ensure that [Docker](https://www.docker.com/) is installed on the machine that the Dev Container will be running on. This could be your local device or on a [remote machine](https://code.visualstudio.com/docs/devcontainers/containers#_open-a-folder-on-a-remote-ssh-host-in-a-container).
 
-### Setup the PostgresQL database
+### Setup the PostgreSQL database
 
 To begin, navigate to the project directory. If working remotely, SSH into your remote environment and locate your source files. To fully set up your PostgreSQL container with testing credentials, execute the Docker Compose file by running:
 
@@ -32,7 +32,7 @@ You can set up the development environment by executing the following command:
 make install-dev PREFIX=/home/build/ovirt/
 ```
 
-Running this command will initiate the application's build process. You can skip tests by appending the `SKIP_TESTS=1` flag to the previous command. Additionally, you can specify the installation directory using the `PREFIX` flag.
+Running this command will initiate the application's build process. You can skip tests by prepending the `SKIP_TESTS=1` environmental variable to the previous command. Additionally, you can specify the installation directory using the `PREFIX` flag.
 
 ### Run the oVirt Engine setup
 
@@ -60,16 +60,16 @@ To enable image uploading and downloading through the administration portal, you
 ovirt-imageio --conf-dir /home/build/ovirt/etc/ovirt-imageio
 ```
 
-> If encountering a certificate error during connection testing, you'll need to accept the certificate in your browser. You can either locate the URL by accessing your browser's network console, clicking the 'Test Connection' button, and visiting the URL showing the error, OR simply navigate to `https://HOSTNAME:54323/info/` and accept the certificate.
+> If encountering a certificate error during connection testing, you'll need to accept the certificate in your browser. You can either locate the URL by accessing your browser's network console, clicking the 'Test Connection' button, and visiting the URL showing the error, OR simply navigate to `https://HOSTNAME:54323/info/` and accept the certificate. Alternatively you can install the oVirt generated CA as a trusted CA in your browser.
 
 ### Connecting via console to your VM instance
 
-To establish a connection to the VM console via noVCN, you'll need to initiate the websocket service:
+To establish a connection to the VM console via noVNC, you'll need to initiate the websocket service:
 
 ```
 /home/build/ovirt/share/ovirt-engine/services/ovirt-websocket-proxy/ovirt-websocket-proxy.py start
 ```
 
-Afterward, head to your newly created VM and select the 'v' arrow adjacent to the 'Console' button. Proceed to 'Console Options' and set 'Console Invocation' to 'noVCN'. Save these settings and click on the 'Console' button.
+Afterward, head to your newly created VM and select the 'v' arrow adjacent to the 'Console' button. Proceed to 'Console Options' and set 'Console Invocation' to 'noVNC'. Save these settings and click on the 'Console' button.
 
 Upon encountering the error message "Something went wrong, connection is closed," please note that this is expected behavior. To proceed, you must accept the SSL certificate in your browser. Access your browser's development console, copy the `wss://XXXXX` URL, and paste it into your browser's URL bar. Replace `wss` with `https` and navigate to the URL. Here, you can accept the certificate. You can reopen the console via the oVirt administrator panel.

frontend/webadmin/modules/pom.xml

@@ -43,7 +43,7 @@
     <gwt-plugin.extraJvmArgs>-Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory -Dgwt.jjs.maxThreads=4 -Djava.io.tmpdir="${project.build.directory}/tmp" -Djava.util.prefs.systemRoot="${project.build.directory}/tmp" -Djava.util.prefs.userRoot="${project.build.directory}/tmp" -Djava.util.logging.config.class=org.ovirt.engine.ui.gwtaop.JavaLoggingConfig ${gwt.jvmArgs}</gwt-plugin.extraJvmArgs>
     <!-- Control target browsers for GWT compilation, maps to 'user.agent' deferred binding property in *.gwt.xml -->
     <!-- By default, compile for Firefox browser only, use 'all-user-agents' profile to compile for all browsers -->
-    <gwt.userAgent>safari</gwt.userAgent>
+    <gwt.userAgent>gecko1_8</gwt.userAgent>
     <!-- Control target locales for GWT compilation, maps to 'locale' deferred binding property in *.gwt.xml -->
     <!-- By default, only English locale is supported, see 'all-langs' profile for a complete list -->
     <gwt.locale>en_US</gwt.locale>