summaryrefslogtreecommitdiffstats
path: root/apps/files_sharing/api/server2server.php
Commit message (Collapse)AuthorAgeFilesLines
* Add the item name to the federated sahre activityJoas Schilling2015-07-021-1/+1
|
* Use the app constant to fix the groupingJoas Schilling2015-07-021-8/+10
|
* Use the item name when refering to the unaccepted remote shareJoas Schilling2015-07-021-1/+7
|
* Update license headersJenkins for ownCloud2015-03-261-13/+12
|
* Correctly get the unique mountpoint name when mounting the shareJoas Schilling2015-03-171-2/+0
| | | | | | | Previously the mount name was checked for uniqueness prior to inserting the share. This caused problems, when two shares with the same name where done or folder, mount point, local share with the same name was done, between sending and accepting of the remote share
* Revert "Updating license headers"Morris Jobke2015-02-261-11/+14
| | | | This reverts commit 6a1a4880f0d556fb090f19a5019fec31916f5c36.
* Updating license headersJenkins for ownCloud2015-02-231-14/+11
|
* rename 'server-to-server sharing' to 'federated cloud'Bjoern Schiessle2015-01-291-4/+4
|
* use uid provided by setupfs hook to mount server2server shares, otherwise ↵Bjoern Schiessle2015-01-261-2/+3
| | | | mount will fail for public link shares
* Next step in server-to-server sharing next generation, see #12285Bjoern Schiessle2014-12-191-17/+34
| | | | | | | | | | | | | | Beside some small improvements and bug fixes this will probably the final state for OC8. To test this you need to set up two ownCloud instances. Let's say: URL: myPC/firstOwnCloud user: user1 URL: myPC/secondOwnCloud user: user2 Now user1 can share a file with user2 by entering the username and the URL to the second ownCloud to the share-drop-down, in this case "user2@myPC/secondOwnCloud". The next time user2 login he will get a notification that he received a server-to-server share with the option to accept/decline it. If he accept it the share will be mounted. In both cases a event will be send back to user1 and add a notification to the activity stream that the share was accepted/declined. If user1 decides to unshare the file again from user2 the share will automatically be removed from the second ownCloud server and user2 will see a notification in his activity stream that user1@myPC/firstOwnCloud has unshared the file/folder from him.
* OCS API for server-to-server sharingBjoern Schiessle2014-12-041-0/+224