<div dir="ltr">Hi<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 10, 2014 at 2:29 AM, Alex Mandel <span dir="ltr"><<a href="mailto:tech_dev@wildintellect.com" target="_blank">tech_dev@wildintellect.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Actually there is a way to handle this.<br>
Puppet <a href="http://puppetlabs.com/" target="_blank">http://puppetlabs.com/</a><br>
<br>
The computers running a puppet client will check the master at a given<br>
time interval any files not matching the master conf will be reverted.<br>
You can also use this to install plugins or QGIS itself and repair the<br>
installation of them easily.<br>
<br></blockquote><div><br></div><div>And you could also write a fabric script to do this very easily (and if you want to be super nice contribute it to my fabgis[2][3] project).</div><div><br></div><div>[1] <a href="http://fabfile.org">fabfile.org</a></div>
<div>[2] <a href="http://fabgis.linfiniti.com/">http://fabgis.linfiniti.com/</a></div><div>[3] <a href="https://github.com/timlinux/fabgis">https://github.com/timlinux/fabgis</a></div><div><br></div><div> </div><div>Regards</div>
<div><br></div><div>Tim</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Enjoy,<br>
Alex<br>
<br>
PS: Yes windows machines can be puppet clients (server might need to be<br>
a nix machine)<br>
<div class=""><div class="h5"><br>
On 03/09/2014 02:19 PM, Zoltan Szecsei wrote:<br>
> On 2014/03/09 22:48, Blumentrath, Stefan wrote:<br>
>> Hi Richard,<br>
>><br>
>> A platform independent solution would be an elegant solution.<br>
>><br>
>> What we do (on Windows) is having a folder on a server containing QGIS<br>
>> default settings (e.g. reg-files for DB-connections, Connections for<br>
>> web services, but also, most popular plugins, map and print composer<br>
>> templates). These default settings can be imported by the users by<br>
>> executing a simple batch-script we produced for that purpose. If that<br>
>> is of interest for somebody I could post the content of the .bat file...<br>
>><br>
>> From that starting point, colleagues can adjust the default settings<br>
>> to their personal needs and preferences...<br>
> This is great - the extra step that I would like to see is that it is<br>
> not only built in and automated, but has controls whereby an<br>
> administrator could "force" certain PCs on the network to only be able<br>
> to use the configs stipulated by the master installation of QGIS.<br>
> When one is managing 15+ PCs it is not trivial to make sure that you<br>
> have copied identical configs to all of them, and to know when someone<br>
> has kindly messed up one of your production PCs.<br>
> Rgds,<br>
> Zoltan<br>
>><br>
>> Cheers<br>
>> Stefan<br>
>><br>
>><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:qgis-developer-bounces@lists.osgeo.org">qgis-developer-bounces@lists.osgeo.org</a><br>
>> [mailto:<a href="mailto:qgis-developer-bounces@lists.osgeo.org">qgis-developer-bounces@lists.osgeo.org</a>] On Behalf Of Richard<br>
>> Duivenvoorde<br>
>> Sent: 9. mars 2014 20:28<br>
>> To: Tim Sutton; Zoltan Szecsei<br>
>> Cc: <a href="mailto:qgis-developer@lists.osgeo.org">qgis-developer@lists.osgeo.org</a><br>
>> Subject: Re: [Qgis-developer] Common QGIS Plugin configuration accross<br>
>> multiple Linux users<br>
>><br>
>><br>
>>> ~/.qgis2<br>
>>> and<br>
>>> ~/.config/QGIS<br>
>>><br>
>>> You could e.g. rsync the user plugin dirs from a central one, or put<br>
>>> them in an nfs mount (read only might have issues as plugins try to<br>
>>> write .pyc files or even write data to the plugin dir).<br>
>>><br>
>>> The ~/.config/QGIS/QGIS2.conf is a standard ini style config file so<br>
>>> you should be able to pick through it and awk/sed/bash your way to<br>
>>> nirvana :-)<br>
>> I'm actually thinking about to make this OS independent, by creating a<br>
>> 'save QSettings' as file option. Then with a command line option you<br>
>> would be able to (just before reading the QSettings) actually<br>
>> read/write this settings file back into user settings. Thereby making<br>
>> it possible to for example transfer a certain setup across a class<br>
>> room (as long as the plugins are available in .qgis2 off cours).<br>
>><br>
>> Would this work? Or do I miss something?<br>
>><br>
>> Regards,<br>
>><br>
>> Richard Duivenvoorde<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Qgis-developer mailing list<br>
>> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Tim Sutton - QGIS Project Steering Committee Member<br>==============================================<br>Please do not email me off-list with technical<br>
support questions. Using the lists will gain<br>more exposure for your issues and the knowledge<br>surrounding your issue will be shared with all.<br><br>Irc: timlinux on #qgis at <a href="http://freenode.net" target="_blank">freenode.net</a><br>
==============================================</div>
</div></div>