QFieldCloud Feature Requests

Currently I prepare a QGIS Project. This is typically located on a local drive within the file strucutre I use for my project work. So something line c:\users\<user>\documents\jobs\<jobref>\. Lets call this the 'original QGIS project'. I then create a qfieldcloud project, as oart of which QFieldCloud creates 'a local copy' of the QFieldCloud project. After I have carried out my field data capture and pushed data to the cloud, I can only sync back to the local copy of the QFieldCloud project, not the 'original QGIS project'. This is very unhelpful. The 'original QGIS project' may contain layers and configuration not included in the the QFieldCloud project. One should be able to synchronise back to the 'original QGIS project'. A seperate issue is that when creating a QGIS project, the QFIeldCloud packager complains if datasets are not in the project folder. But that is a requirement of the QFIeldCloud project, not the source QGIS project...the packaage should handle this and only identify specific issues, for instamce when non-local files or datasources are unavailable.

As a QFieldCloud user, I want to exclude certain files from file versioning or protect them from getting updated, so that my storage is not quickly filled up by layers that are not editable and should not be updated every time the project is synchronized.

Currently, enabling cross-origin access to the API requires manually adding add_header directives in the nginx configuration. This makes it cumbersome for developers who want to build custom frontends or applications against the QFieldCloud API. To simplify this, we should manage CORS directly at the Django level using environment variables instead of hardcoded nginx headers. Proposed Changes Add django-cors-headers as a dependency Configure CORS middleware and settings in settings.py , driven by environment variables: -- CORS_ALLOWED_ORIGINS= https://app.example.com,http://localhost:5173 -- CORS_ALLOW_CREDENTIALS=1 Restrict CORS handling to /api/ endpoints via CORS_URLS_REGEX Remove hardcoded Access-Control-Allow-Origin header from nginx (e.g. /swagger.yaml) Ensure https://docs.qfield.org is configured via .env instead of nginx Pass CORS_ALLOWED_ORIGINS and CORS_ALLOW_CREDENTIALS through docker-compose.yml Update .env.example with documentation Expected Outcome Developers can build their own frontends against the API by simply adding their origin to CORS_ALLOWED_ORIGINS — without modifying nginx configuration or rebuilding containers.

A web map viewer capable of a minimal web map rendering of the uploaded .qgs/qgz files a fit that would require qgis-server ofcource something similar to QWC2 at https://qwc2.sourcepole.ch/?t=qwc_demo&l=edit_points%2Cedit_lines%2Cedit_polygons%2Cgeographic_lines%2Ccountry_names%2Cstates_provinces%2Ccountries&bl=mapnik&c=1740775%2C3057935&s=25000000 Repo at https://github.com/qgis/qwc2

If you have a lot of projects, it would be nice if there was a function like a search bar to make it easier to find projects.

As a project admin, I want to receive email notifications in case of errors such as delta apply failures, job failures, or when the project status turns red, So that I can quickly respond to these issues, prevent data loss, and maintain the smooth operation of the project.

As a field worker, I need to duplicate existing projects within QFieldCloud to swiftly create new ones based on templates without opening QGIS. (Source: https://github.com/opengisch/QField/discussions/3111 )

We would find it useful to access storage used by an organization through API. Our self-hosted QFC allows one storage plan across all organizations so we need a way of monitoring storage used by each organization. It would also be useful to get individual project storage usage.

It would be good if you could sort projects by size, or if you could see directly in the overview on the QFC website how big the project is and how much storage it takes up.

Problems: QFieldCloud is currently only accessible via ipv4 QFieldCloud tries to connect to PostgreSQL Databases only via ipv4 It would be great to have ipv6-enabled QFieldCloud to access ipv6-only PostgreSQL Server. Since many hosting and internet provides only supply a public ipv6 and no public ipv4 address.