You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow users to use qgis projects saved to postgresql, not only for local projects.
Description:
Qgis projects can be shared and used by multiple people or by one person but with different devices. There comes handy tool such as saving and loading projects from postgresql database.
Currently Bridge does not support projects saved to pg - it throws an error that the project is not saved (although it is - in database) since the project does not have a "file". It makes Bridge unusable in such case. It makes users have to save projects as a local copy and only with that local copy publishing is possible. That action can lead to unwanted forking of single qgis project and adds unwanted workspaces in geoserver.
Goals:
Allow users to use postgresql as a project store when publishing data/ styles.
Additional Notes:
This should be related to another request - allowing users to select into which geoserver workspace styles and data should be saved.
@jakusp Thanks for your suggestion.
Would it also be fine if we only added the possibility to provide a custom name for a workspace or select an existing target workspace (to add to)? The need to read the project name would become less important in that case.
Summary:
Allow users to use qgis projects saved to postgresql, not only for local projects.
Description:
Qgis projects can be shared and used by multiple people or by one person but with different devices. There comes handy tool such as saving and loading projects from postgresql database.
Currently Bridge does not support projects saved to pg - it throws an error that the project is not saved (although it is - in database) since the project does not have a "file". It makes Bridge unusable in such case. It makes users have to save projects as a local copy and only with that local copy publishing is possible. That action can lead to unwanted forking of single qgis project and adds unwanted workspaces in geoserver.
Goals:
Additional Notes:
References:
The text was updated successfully, but these errors were encountered: