According to the docu (https://dev.qfield.cloud/documentation/advanced_setup.html#postgis), the PostGIS DB needs to be accessible to the world in order to be able to sync PostGIS Layers with the cloud. Together with the need to store username/password in clear-text in the qgis-project, I imagine that this is a “security-no-go” for many organizations.
Is an alternative, safer approach planned for the future, e.g. transferring gpkgs to the desktop and letting QFieldSync handle the (local) syncing to the DB? If yes, when?
Thanks a lot and cheers!
Nico
Imported from GitHub discussion by @nischmi1 on 2021-09-17T14:03:59Z
Hello, nischmi1 . The security-no-go you have seen is indeed something we are aware of. There are some planned improvements on this front. The one that is coming the next few months is uploading the .pgservice file on the cloud, so the credentials are not stored in plain text in the project file.
What you can already do is making your PG database open only for the IP range that app.qfield.cloud uses.
The proposed solution with QFieldSync syncing the PG database locally is not planned for now.
Imported from GitHub comment by @suricactus on 2021-10-03T17:58:17Z
In order to provide a clearer and more manageable discussion forum and to have all discussions about QField and related products (i.e. QFieldCloud and QFieldSync) in a single place, we transferred all the discussions from the QFieldCloud to the QField repository.
Imported from GitHub comment by @marioba on 2022-02-01T13:28:49Z