[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-users
Subject:    Re: Seafile with Kolab on Nginx?
From:       Milan Petrovic <petrovic.milan () gmail ! com>
Date:       2016-01-10 8:57:16
Message-ID: CAPGMBao7t4uT5Hz+T23EyckuN7Po+PqtgMOfCDS4E3F+==dxyg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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@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@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@lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
>

[Attachment #5 (text/html)]

<div dir="ltr">Thanks Daniel,<div><br></div><div>What actually made me ask this is \
that all the descriptions of Seafile integration were having an Apache config change \
part and I couldn&#39;t quite translate those into a meaningful Nginx conf \
change.</div><div><br></div><div>I&#39;ve ended up (last night) moving Seafile to its \
own subdomain, updated its and Kolab&#39;s config files and, even without touching \
Nginx at all (except for reconfiguring it for subdomain) - everything seems to work \
so far.</div><div><br></div><div>Thanks again, Milan.</div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 9, 2016 at 11:33 PM, \
Daniel Hoffend <span dir="ltr">&lt;<a href="mailto:dh@dotlan.net" \
target="_blank">dh@dotlan.net</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi MilanI don&#39;t see any issues. I&#39;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.<br> \
<br> In the end you&#39;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<br> <br>
Hope that helps.<br>
<br>
--<br>
mfg<br>
Daniel Hoffend<br>
<div><div class="h5"><br>
&gt; Am 31.12.2015 um 00:51 schrieb Milan Petrovic &lt;<a \
href="mailto:petrovic.milan@gmail.com">petrovic.milan@gmail.com</a>&gt;:<br> &gt;<br>
&gt; Anyone has any experience integrating Seafile with Kolab, both on Nginx and same \
server?<br> &gt;<br>
&gt; 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.<br> &gt;<br>
&gt; Thanks!<br>
</div></div>&gt; _______________________________________________<br>
&gt; users mailing list<br>
&gt; <a href="mailto:users@lists.kolab.org">users@lists.kolab.org</a><br>
&gt; <a href="https://lists.kolab.org/mailman/listinfo/users" rel="noreferrer" \
target="_blank">https://lists.kolab.org/mailman/listinfo/users</a><br> \
</blockquote></div><br></div>



_______________________________________________
users mailing list
users@lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users

[prev in list] [next in list] [prev in thread] [next in thread]