Seafile with Kolab on Nginx?

[Milan Petrovic]

Thanks Daniel,

What actually made me ask this is that all the descriptions of Seafile
integration were having an Apache config change part and I couldn't quite
translate those into a meaningful Nginx conf change.

I've ended up (last night) moving Seafile to its own subdomain, updated its
and Kolab's config files and, even without touching Nginx at all (except
for reconfiguring it for subdomain) - everything seems to work so far.

Thanks again, Milan.

On Sat, Jan 9, 2016 at 11:33 PM, Daniel Hoffend <dh at dotlan.net> wrote:

> Hi MilanI don't see any issues. I've seafile and kolab running on the same
> server using nginx as webserver. Okay seafile is on a different subdomain
> as kolab but even on a single domain there should be no problem as long as
> you follow the guide on how to install seahub in a non-root domain.
>
> In the end you'll end up with three location entries. One for the
> webfrontend seahub /seafile, one for static web resources (images,css,js)
> /seafmedia and one for the ccnet /seahttp
>
> Hope that helps.
>
> --
> mfg
> Daniel Hoffend
>
> > Am 31.12.2015 um 00:51 schrieb Milan Petrovic <petrovic.milan at gmail.com
> >:
> >
> > Anyone has any experience integrating Seafile with Kolab, both on Nginx
> and same server?
> >
> > Also, in my setup, both apps (Kolab suite and Seafile) are on the same
> subdomain, meaning Seafile is in mydoman.tld/seafile which made my trials
> harder so far.
> >
> > Thanks!
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20160110/f5a0e675/attachment.html>