On 2018-08-20 20:55:46 +0200 (+0200), Alexander Wirt wrote: > On Mon, 20 Aug 2018, Jeremy Stanley wrote: > > > On 2018-08-20 20:05:42 +0200 (+0200), Alexander Wirt wrote: [...] > > > https://docs.gitlab.com/ee/administration/repository_storage_paths.html > > > https://docs.gitlab.com/ee/workflow/lfs/lfs_administration.html#storing-lfs-objects-in-remote-object-storage > > > https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template#L176 > > > https://salsa.debian.org/salsa/salsa-ansible/compare/e709949d0e174f9503b757c95cebee79f0ffe9b0...aafc7392e90efc21fa7e1858eee214029b29764c > > > > > > its all there. > > > > Part of the open-core challenge I'm afraid. I already spoke with one > > "cloud" service provider last week who was willing to follow up to > > this thread with an offer to donate whatever storage types are > > needed, but we couldn't find documentation explaining supported > > storage options for Gitlab *CE* (note the "ee" in those > > documentation URLs, they're the same ones I already found). Is it to > > be assumed, generally, that Gitlab's Enterprise Edition > > documentation is also appropriate for Community Edition deployments? > https://docs.gitlab.com/ce/administration/repository_storage_paths.html > > if you can replace ee with ce in the url it is also valid for ce. > jftr afaik gitlab uses fog[1] for cloud storage, maybe that knowledge helps. > > Alex > > [1] https://github.com/fog/fog I had actually tried that on a whim with some of the EE documents I found last week, but I guess I tried it on the wrong ones. In particular https://docs.gitlab.com/ce/workflow/lfs/lfs_administration.html#storing-lfs-objects-in-remote-object-storage does seem to confirm CE supports whatever Fog does, so pretty much anything in that case. Thanks! (Also, no need to Cc me, I've been subscribed to and at least skim most everything which passes through this list for something like two decades now.) -- Jeremy Stanley
Attachment:
signature.asc
Description: PGP signature