Self-hosted user/project interface

[qwenger]

What is the bug or the crash? What were your expectations and what actually happened?

When self-hosting, one gets access to the admin web interface (a standard Django admin interface, as shown in https://docs.qfield.org/reference/qfieldcloud/self_hosted/django_interface/).

However, it looks like the user/project interface (advertised in https://docs.qfield.org/get-started/tutorials/get-started-qfc/#qfieldcloud-overview) isn't included. At least I couldn't find any trace of its source code in the repo.

This would also explain some long-standing and unanswered issues (#842, #1434, ...).

So: is it simply so that the hosted/commercial web interface isn't part of this repo and as such not part of QFieldCloud as a FOSS? That would be quite disappointing coming from a team that uses "Open-source" so much in its branding. Plus the front and doc pages should make it clearer that app.qfield.cloud isn't part of QFieldCloud. Currently it's misleading at best and straight-up deceiving at worst. An official stance would be appreciated.
If instead that app does belong to the FOSS project, then please show us where its source is available (and please, please answer and fix the aforementioned issues).

Thank you in advance.

Steps to reproduce the issue

Refer to the aforementioned issues.

Version

3d4a9cb (HEAD -> master, origin/master, origin/HEAD) Merge pull request #1461 from opengisch/QF-6039-object-storage-cleanup-script-simple

Operating system name

Other (please specify in additional context)

Operating system version

not relevant

Reinstall QFieldCloud

• I have a fresh install of the latest QFieldCloud version, but the problem persists.
• I have the latest available Docker engine installed on my machine.
• Problem can be reliably reproduced, doesn't happen randomly.

Additional context

No response

[t-book]

Hey, just to chime in here — I'm not a QFieldCloud dev, just someone self-hosting and administering it independently.
From what I understand, yes, the web frontend at app.qfield.cloud is not part of the open-source project. It appears to be tied to the OpenGIS.ch subscription/payment model, which makes sense from a business perspective and is understandable that it's not included in the OSS repo. Personally I'm fine with that — we already get a lot out of QFieldCloud's core as it is.
The good news is that QFieldCloud uses Django REST Framework, so the API is there for anyone to build their own frontend. You can access pretty much everything except the User Model from what I saw last time I looked at the API.