-
Notifications
You must be signed in to change notification settings - Fork 663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a multi-account feature [$474 awarded] #43
Comments
+1 how is the state of development on this? |
Not coming in the near future, since some major refactoring is required first. |
ok, thanks. |
+1 -- if this means, it should be possible to access different owncloud servers with one desktop client -> desperately needed (mac user here) Reason: I maintain a private family cloud and another one for a non-profit advocacy group. At the moment, I can only use the client for one of these cloud servers and have to maintain the other via web interface. |
yes, I'd really love this feature because my company has got it's owncloud, our customer too, and maybe a private owncloud for one of my favorite non-profit organisations will be setup in near future... |
another solution would be to allow installing OwnCloud client several times in parallel with different configs (for each required server/user combination) before refactoring thousands of code lines? |
No need to +1. We would all love to see it, but it's a lot of work. We also thought about the multi-config option, but also that isn't zero-effort. Rest assured it's on the list. |
+1, too! |
I've managed to run two instances of owncloud client on Mac OS X with different configs. There are some drawbacks (it doesn't save your password, you have to run it through terminal) but at least it seems to work. |
Another possible workaround is to enable the External Storage Support app in at least one of the OwnCloud instances, then add the other OwnCloud instance to your account as "external storage" (using the "ownCloud/WebDAV" option, entering your WebDAV URL, and nothing as the Root to allow access to everything) Once it's added, you should be able to use it in the client as you would any other sync folder... |
Is there somebody working on it ? |
+1000 ;-) |
Hi, p.s. Br. Mladen Sent from my iPad On 21. jun. 2013, at 18:03, jmhermelin notifications@github.com wrote:
|
@guru4hp power shell script is warmly welcome :-) |
Couldn't you simply move the cfg file into the working folder thus allowing us to install multiple versions of ownCloud client? Just wondering if there is a reason why the cfg file is store in the AppData folder. It sounds like a simple fix, but I don't understanding the programming end, maybe this isn't possible. |
@lonlyboy almost everything is possible. It just has to be done, somebody has to put the hammer out and hit the anvil. And before we can get to this Enhancement stuff we will need to nail all bugs out that make this client unreliable in any way. I think that is good for us all... Best is you find your programming friend and convince him to jump on client development :-D |
+1 ----- A very useful feature |
In Windows, you can use Task Scheduler to create a task to run when you log in to Windows. You can specify user account and password to run the task as. In Windows 7, make sure you set the following properties for the task: [Triggers Tab] [Actions Tab] [Conditions Tab] [Settings Tab] [History Tab] When you save the Task, you will be prompted for the password for the user account you specified in the security options section of the General tab. You may also get a message about "Log on as batch rights". I used the information from this link to give the user account "Log on as batch". NOTE: While this will launch OwnCloud as another user and start syncing files, you will not be able to access the interface for the other instance of OwnCloud. This shouldn't be a problem, as it should not be necessary to access the OwnCloud interface after initially setting up the synced folders for the other user account. Also, you can just run another instance of OwnCloud using the method above to get to the interface for the other user. |
I have a different approach to the multi account feature. I have been reading about it and if i am not misstaken the feature will not be implemented in the near future due to the fact that it is an aweful lot of work. I suggest to have an additional switch to the commandline tool instead, where you can run the sync client once --sync_once. It will then sync once and then quit after syncing. With this option we will be able to write a batch script that runs one instance after the other sequentially. greets mike |
As a workaround, I made a copy of the binary and renamed it to C:\Program Files (x86)\ownCloud\owncloud2.exe. Then I created a shortcut to it and updated the properties to point the shortcut to a newly created directory for the configuration files: "C:\Program Files (x86)\ownCloud\owncloud2.exe" --confdir "C:\Users\david\owncloudconf2" So far it's been working fine, but I'm a little concerned that it seemed a little too easy, and there's got to be a catch. Can the two instances running under the same account stomp on each other? I dunno... I'm not a Windows programmer, and I'm not familiar with the owncloud code so I'm flying an experimental here. |
@quaboag i tried your workaround but i'm able to start 2 instance of owncloud client but they run on same server even if I indicated two different url server in the configuration file. |
On Windows the only problem I have is that the original ownCloud instance will no longer start on boot. I'll toss a shortcut into the startup folder and see if that makes a difference. I tried the same trick on CentOS 6 and it's working fine there. I'm running three instances. Two of them are two different accounts on a single ownCloud server running on a private vpn. The third is running on a private ownCloud server that's Internet facing. Are you syncing to three different folders, or are you syncing all of them to the same %HOMEPATH%\ownCloud (or $HOME/ownCloud) folder? I'm not syncing them to the same folder.... I would expect that the .csync_* files would overwrite each other. For my CentOS experiment I ran this (doing this from memory--apologies for typos): cd ; mkdir bin ; cd bin and to run them.... nohup $HOME/bin/owncloud2 --confdir $HOME/owncloudconf2 & ...and pick a different sync folder in the gui install (e.g. the $HOME/owncloud[23]). (You might want to backup the $HOME/ownCloud folder just in case you can't cancel the initial sync in time.) |
Hi quaboag , "c:\Program Files\ownCloud2\owncloud2.exe" --confdir c:\Users\xxx\AppData\Local\ownCloud2\owncloud2.cfg "[General] [Settings] [ownCloud] [Proxy] [LogBrowser] then i lounch the second one: "c:\Program Files\ownCloud2\owncloud.exe" --confdir c:\Users\xxx\AppData\Local\ownCloud\owncloud.cfg [Settings] [ownCloud] [Proxy] [LogBrowser] and where "C:\Users\xxx\AppData\Local\ownCloud\folders\ownCloud" is [ownCloud] and and where "C:\Users\xxx\AppData\Local\ownCloud2\folders\ownCloud2" is [ownCloud2] Can i ask you where is my mistake? Thanks |
Gigisco: |
lonlyboy: "c:\Program Files\ownCloud\owncloud.exe" --confdir c:\Users\xxx\AppData\Local\ownCloud\owncloud.cfg" but i see the same problem...it start the same process and the second doesn't sinc any folders. i'm wrong in something? |
@eslindsey That sounds great! It would be good if you could join #owncloud-client-dev on Freenode to discuss this. |
@eslindsey still interested? |
@danimo I see why this hasn't been done yet. This won't be an overnight fix. :) Yes, I am still interested, since this is a major feature requirement for me. School and other work takes priority at the moment; hopefully I can engage this project in about a month. I'll see you guys on IRC when I've got some free time. |
I would object to list the redesign of the settings dialog here. That is a different feature and adds more, unneeded complexity here. |
Shucks, that's probably the easiest thing on that list. ;) But I agree that UI design is not directly related to the addition of this feature.
|
I tryed an different approach. PS. "test" is "test" in portuguese
Running the bat file, the owncloud program executes like a fresh install and don't see the lock files created by other owncloud.exe instances. But I think the best way is creating a .vbs file instead of .bat file. |
This issue doesn't need more +1s. We all understand that everyone wants this feature. Comments like this (not to pick on you personally) don't contribute anything to the discussion and simply take up space in people's inboxes. What this issue does need is patches. |
#2565 has the necessary changes to move the different pages on top as already existing on OS X. The next step will be to refactor the |
I've got a simple workaround for those who need to sync multiple accounts (even with multiple owncloud instances) using owncloudcmd.exe, you can find my article here: |
Hello, i wrote for me a small wordpress site, see - http://www.mosandl.eu/2014/04/start-owncloud-sync-client-twice/ cheers |
Note that all the workarounds will cause issues, such as overlay icons not working reliably. |
for me, tested in mac and windows i have no issues right now |
Avoid accessing the global account instance and instead pass it in from the outside.
Also fix a possible bug with the share dialog when no account is configured.
are there any news concerning this awesome feature? We are really looking forward for this. |
We know, but it's scheduled for 1.9, and we are still working on 1.8. That said all code changes are being developed with multi account in mind already. |
+1 I could really use that feature. The workarounds are not that comfortable. |
+1 |
1 similar comment
+1 |
Guys, the feature is scoped and being worked on. Every time you post a +1 not only does God kill a kitten, but every developer gets a mail that he needs to process, taking more time from completing features like this. For now, it seems I'll have to lock this issue :-( |
New issue to track progress: #3084 |
I refer to the Windows Client 1.1.1 .
Problem:
I want to synchronise different Users' directories, on a same or different ownCloud installations.
Currently, I do not see a possibility to achieve this in the current version and suggest this as improvement. Please correct me if I am wrong.
Remark:
In the current version, the following appears to be implemented (single user, single server, plurality of directories)
The text was updated successfully, but these errors were encountered: