Install nextcloud on a existing web site as a subpath (http://example.com/nextcloud)

[aalaesar]

User may just want to install a nextcloud instance as a subfolder of another website /domain

[aalaesar]

@noplanman I'm quite puzzled about this one. Specially with nginx. I'm not sure it is possible to do it as easy as in Apache2, adding a directory.

I mean: changing the pattern to add the directory path is simple but i'm not sure how to implement the resulting conf file into an already existing nginx configuration without breaking things. You seems to know much more than me about web design & config.

[noplanman]

It should be the same as on Apache, just put the config file into /etc/nginx/sites-available and then simlink it into /etc/nginx/sites-enabled. That's also how Apache does it, right? (I'm not all too familiar with Apache 😄)

[aalaesar]

So Are you saying that nginx accept multiple server blocks with a identical server_name and port statements and will merge their conf ?

In fact, I did'nt well explained myself: Let say that a user have some website configured to be served at http(s)://example.com He wants to add a nextcloud instance on his server and wants it at http(s)://example.com/nextcloud or whatever the path could be...

How can the role add nextcloud to his existing configuration:

• if he's using apache2 ?
• if he's using nginx ?

without breaking things... For apache2, an example has already be given in the nextcloud's doc The nginx conf example is a self contained server block and I'm not sure if adding another server block for the same port and server_name might work. this may require other templates...

[noplanman]

Ok, I understand now.

I think for that case the best would be to serve nextcloud on a separate internal port and then proxy the request, which would be added manually by the user in their existing config.

I guess it could be possible to add it with ansible with blockinfile, but it may be a bit difficult depending on the complexity of an existing configuration.

[aalaesar]

Than you for your response @noplanman . I'm putting this one on hold, giving that it may be much more difficult than expected to add this feature. I'll read some books on nginx in the following weeks, maybe i'll find something usefull...

[staticdev]

@aalaesar this one has removed help wanted but still not done right? Do you have plans for it?

[aalaesar]

@aalaesar this one has removed help wanted but still not done right? Do you have plans for it?

I think I'll drop it. I'll do a quick search in the doc, if I find elements against it, it will be close. Since I opened it nobody requested the feature, neither proposed help.

[aalaesar]

@aalaesar this one has removed help wanted but still not done right? Do you have plans for it?

I think I'll drop it. I'll do a quick search in the doc, if I find elements against it, it will be closed. Since I opened it nobody requested the feature, neither proposed help.

[staticdev]

@aalaesar I think I would also not invest time on it and close as wont do.