[qgis-qwc2] QWC-services without Docker?

[Sandro Mani]

Hi Thomas

> What still confuses me is whether the qwc-services can/should be built into my existing qwc-demo-app, or whether a new QWC is/would have to be created this way?

The qwc2-app per se is able to work standalone, you can extend its 
functionality by using qwc-services, but it is not required. If you 
decide to use the qwc-services, then you need the qwc-map-viewer service 
to serve your application (since it will ensure that i.e. the 
themes.json will be delivered to the client according to the configured 
permissions).

> For a start, could I include a simple (i.e. without further dependencies) qwc-service and which one would that be? (permalink-service?)

As an core set of services, you'll want:

qwc-config-generator (generates service configurations)
qwc-admin-gui (the admin backend for managing users and permissions)
qwc-config-db (stores user and permissions as configured in the admin-gui)
qwc-db-auth (user authentication service, against the users stored in 
the config-db)
qwc-ogc-service (proxy between the client and the QGIS Server, enforcing 
the map resource permissions)
qwc-map-viewer (serves the application, as outlined above)

qwc-services-core is pulled in via requrements.txt in the respective 
service dependencies. You don't need to take care of it separately.

Best
Sandro