owncloud / client

🖥️ Desktop Syncing Client for ownCloud
GNU General Public License v2.0
1.4k stars 665 forks source link

Store/sync settings of owncloud client on server #1597

Open ronaldotto opened 10 years ago

ronaldotto commented 10 years ago

New feature. When the mirall client is setup, it stores it settings in the account of the user like a file (or in db). So the client creates a file with the name .occwsettings.cfg for Windows settings and .occmsettings.cfg for mac and so on.

So when you install Mirall client on a seccond machine it askes: Should i use the same settings as on you other windows computers? Yes no.. and ready you are.

Makes reinstalling the client easier

dragotin commented 10 years ago

Are you suggesting to sync the file via the ownCloud server? Nice idea. So on a second installation, user just would have to enter the ownCloud URL and user+password and the folder config could be loaded from the server. Mirall than could preset the same folder setup as stored on the server.

ronaldotto commented 10 years ago

Exactly. That might even make it possible for an admin to create a config file so the user just has to install the client with url and credentials and agree to use the pushed settings.

scolebrook commented 10 years ago

+1 for pushing default settings from admin and syncing settings between clients.

One feature I really like about CrashPlan Pro is that the admin can set defaults for all settings and push them to clients, individually or as a whole. If users change their settings it's reflected in the admin console also. So you can push out excludes for preventing backups of virtual machines, set bandwidth throttles, any setting. Great for giving a turn key solution customized to an individuals needs.

The ability to set client options like sync folders (when selective sync is built), excludes, etc would be great for provisioning new users with a ready to go system on first login.

jancborchardt commented 10 years ago

This is a really good idea! That question could be in the setup already, after the username/password check.

stefan-niedermann commented 10 years ago

but then will it be able to use different sync configuration for different clients? Situation: One Server S1, Two Clients C1 and C2.

C1 has a 2 TB Drive, so i want to sync all - images, videos, documents, and so on. C2 has a 60 GB SSD, so i want to sync only the important files - documents.

It would be cool, if client gets the defaults from the user account (if nothing is set, check admin default preferences). But i must be able to overwrite my account-settings on each client.

jancborchardt commented 10 years ago

Well of course either you do all default like the stored config – or you don’t. :)

Think of this more a settings backup rather than settings sync. If you use different settings on two devices, both configs could be saved. Then when you set up a new device, it could ask you if you want to use the config from your e.g. Thinkpad-Laptop or from your Bla-PC.

(We had that discussion in the past with Gnome by the way. ;)

AnrDaemon commented 8 years ago

IMO, what should be stored from client configuration is directorues to sync and user-specified exclusion preferences. Sync location could be anything, different on different installations (how would you match Windows vs. Linux f.e.?). When a new client connecting to the cloud first time, the settings would be downloaded first and presented as one of default choices, instead of/in addition to "sync all"/"configure". I'm also contemplating an idea of automatic profile creation (each client with a deviation from stored settings will save its own settings profile to the server). But that's probably an overcomplication.