Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On Sun, Jul 21, 2013 at 7:07 AM, Florian Effenberger
<floeff@documentfoundation.org> wrote:

thanks a lot for evaluating this!
I've been running ownCloud privately for quite a while, and we also use it
internally at TDF, it performs quite well.

How would you go about the accounts? One large group account, or individual
accounts for everyone?

For edit/write permissions, I agree with Jonathan and suggest that we
go with one account per person -- that would make it easy to ban
someone quickly if they didn't follow the rules.

Can we share files with the general public, or does everyone who wants to
see a file need credentials?


The "Share with link" feature allows us to share a directory so that
it is world-readable. The links are a bit cumbersome (e.g.
http://owncloud.documentfoundation.org/public.php?service=files&t=09db8abe6e3850ab1723fb9ea6a40972
), but we can mitigate that problem by setting up a simple redirect
like:
http://owncloud.documentfoundation.org/public

Cheers,
--R

-- 
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.