[Qgis-user] disabling qgis.db

[Régis Haubourg]

Hi, well I used a python script, and my admin guys rewrote it from scratch
with powershell.

The business logic was this one:

- create a template folder accessible to the init script.
  - in the folder add a  cleaned template QGIS user profile
  - add a "delta" ini file containing all keys you want to add, delete,
update. I used a diff syntax (+ to add, - to delete, nothing to update)
- we add a file flag in each user profile that has been treated
- on session opening:
  - if you don't find the flag, deploy a preconfigured the raw qgis profile
  - if you find the profile. Apply the delta file to maintain the profile

Done.

Cheers
Régis



Le mar. 11 déc. 2018 à 08:46, <Fuenfer-Koenigstein.Benjamin at swm.de> a
écrit :

> Hi Régis,
>
>
>
> thanks for your reply! How did you do it? Python script on session start?
> In my case, it would be OK if e.g. users have their individual GUI settings
> or spatial bookmarks but all connections in browser-panel and default CRS
> should reset to (globally maintained) default on closing QGIS. Do you have
> experience how to implement that?
>
>
>
> Regards
>
> Benjamin
>
>
>
> *Von:* Régis Haubourg [mailto:regis.haubourg at gmail.com]
> *Gesendet:* Montag, 10. Dezember 2018 17:12
> *An:* Fuenfer-Koenigstein.Benjamin IT-LN-TS
> *Cc:* QGIS list
> *Betreff:* Re: [Qgis-user] disabling qgis.db
>
>
>
> Hi Benjamin,
>
> I think the guidelines for software generally assumes that user profiles
> should be in editable location. I'm not sure we can ensure you in the long
> run that you will not face regressions sometimes.
>
> To adress your use case, I used to work with session startup script that
> cleared / reset user profiles on session close or session opening. The
> assumption was to let user free to change their profile settings but not
> for all settings (mandatory plugins for instance, default SRS..)
>
> Cheers
>
> Régis
>
>
>
>
>
> Le lun. 10 déc. 2018 à 16:19, <Fuenfer-Koenigstein.Benjamin at swm.de> a
> écrit :
>
> Hello,
>
>
>
> I have an issue with creating a central QGIS configuration on a network
> drive. The goal is to have one read-only configuration that all users use.
> Generally works like a charm with starting QGIS 3.2 with --profiles-path
> pointing to a read-only dir. Users get the right settings, they still can
> play around but changes are discarded when quitting QGIS. Only problem is
> qgis.db, seems that QGIS necessarily needs write access to that file,
> otherwise it throws an error at start (but works with no problems
> subsequently). Is there any way to avoid that, e.g. starting qigs ‘silent’
> or setting the path to qgis.db to a local user folder? Seems that qgis.db
> doesn’t contain any crucial configuration, though same bookmarks for all
> users would be nice to have.
>
> I’m aware of https://issues.qgis.org/issues/13732 and generally
> understand Nathan’s and Nyall’s point of view but still think it would make
> sense to ignore qgis.db for use cases like mine.
>
>
>
> Thanks for your ideas and help!
>
>
>
> Regards
>
>
>
> Benjamin Fünfer-Königstein
>
>
>
>
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20181211/12a09951/attachment.html>