Installation¶

Released version¶

There is no release yet. The plugin is not on the official QGIS plugin repository, and the releases page is empty. Until then, install the development version below.

Once released, the plugin will be at https://plugins.qgis.org/plugins/geoserver_manager/, and will install directly from the plugin manager. A release zip will also be on the releases page, for Plugins → Manage and Install Plugins → Install from ZIP.

Using this plugin with QGIS Deployment Toolbelt (QDT)¶

To deploy this plugin with QGIS Deployment Toolbelt (QDT), add this snippet to the plugins attribute of your profile.json file:

{
    "folder_name": "geoserver_manager",
    "name": "GeoServer Manager",
    "official_repository": true,
    "plugin_id": null,
    "version": "0.1.0"
}

Replace the version attribute with the version you want to install.

Beta versions¶

The plugin is flagged as experimental. Enable experimental plugins in the settings of the QGIS plugin manager to see it.

Latest development version¶

The plugin is packaged for each commit to main. To test it before a release, add this address as a plugin repository in the settings of the QGIS plugin manager:

https://ronitjadhav.github.io/qgis-geoserver-manager/plugins.xml

This version can be unstable.

Network settings¶

Behind a proxy¶

The plugin goes through the HTTP proxy set in Settings → Options → Network of QGIS, except for the URLs excluded there. Each time the dialog connects, it passes that proxy to Python’s requests, which the plugin and its REST library use. It does so through the HTTP_PROXY and HTTPS_PROXY environment variables of QGIS. Test connection instead hands the proxy of the URL as typed to its own requests, and leaves the variables alone. So:

A variable you set yourself before starting QGIS wins over the proxy of QGIS.
With the DefaultProxy type (the proxy of the system), requests reads the settings of the system itself. It cannot read a proxy auto-configuration (PAC) script: set HTTPS_PROXY then.
A SOCKS proxy is not passed on.
Other Python plugins, and the programs QGIS starts, see the variables too. The variables hold the user name and password of the proxy when it has them, until the plugin is disabled or uninstalled.
After a change of the proxy, press Refresh in the dialog.

A private certificate authority¶

The plugin does not read the certificate store of QGIS. Its requests check the certificate of the server against the certificate authorities (CAs) that Python’s requests knows. For a GeoServer whose certificate comes from a private CA:

Make a PEM file that holds that CA and the usual public ones. For example, copy the bundle of certifi and append the CA to it. In the Python console of QGIS, import certifi; certifi.where() gives the path of that bundle.
Set the REQUESTS_CA_BUNDLE environment variable to that file. Settings → Options → System → Environment of QGIS sets it for QGIS alone. Then restart QGIS.
For the layers the plugin adds to QGIS, also import the CA into the certificate manager of QGIS (Settings → Options → Authentication).

Untick Verify the server’s TLS certificate in the settings of the plugin only as a last resort. It turns the check off for the requests of the plugin, and does nothing for the layers.