[qgis-qwc2] QWC-services without Docker?

[Thomas Schüttenberg]

Hi Sandro,

finally(!), after I was not only occupied with other tasks for weeks, but also had to solve severe problems with the virtual Python environment on Windows, I now can come back to the configuration of the qwc services, or even start with it...

But first, are you aware of any QWC in production use that have also been installed directly under Windows as WSGI modules? 
Based on my current experience[1], it seems to me that this is not really recommendable or at least cannot be successfully implemented with my skills and resources.

Nevertheless, what I have achieved so far is the setup of a virtual Python environment, therein the installation of mod_wsgi as well as the qwc-services you mentioned before including all their requirements. A config-db is also set up according to[2]. The qwc-services (and wsgi) configurations sent by you have been pasted into the Apache webserver config and the (qwc-swevices) root_dir is set.

Because my "hello world" wsgi script is already served, I wonder at what point some of the qwc-services become visible. I understand, that every service has to be configured according to all the others, but having all the different Config.json files it seems VERY complicated to me. 

Mayby the docs are just kept to short for my level of knowledge, but could you please try to point me to a starting point of the service configuartions?

[1] https://github.com/GrahamDumpleton/mod_wsgi/issues/663 
[2] https://github.com/qwc-services/qwc-config-db/blob/master/README.md

Thanks, all the best
Thomas

> Sandro Mani <manisandro at gmail.com> hat am 28.01.2021 11:31 geschrieben:
> 
>  
> 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
> 
> 
> _______________________________________________
> qgis-qwc2 mailing list
> qgis-qwc2 at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-qwc2