Skip to content
This repository has been archived by the owner on Feb 4, 2021. It is now read-only.

Enable changing listen port for NextCloud #13

Closed
wants to merge 1 commit into from

Conversation

Sawn
Copy link

@Sawn Sawn commented Jun 29, 2016

I am using a nginx reverse proxy as an SSL offloader in front of my containers.
As I already had a container using port 80 I needed the possibility to change NextCloud listen port to another one.

@Wonderfall
Copy link
Owner

Wonderfall commented Jun 29, 2016

Hi, thanks for your interest. However, I'm not sure why this is needed.
So, if you're using nginx as a reverse proxy, why would you like to change nextcloud listen port ? All you have to do is link the nextcloud container to the nginx container and use proxy_pass http://nextcloud. If you're not using a nginx container, you can use the IP address of the container like this :

docker inspect nextcloud | grep IPAddress\" | head -n1 | grep -Eo "[0-9.]+" 

In a nutshell, when using a reverse proxy, there's no need to bind the container port to the host. But if you want to do so, Docker allows you, for example, to bind port 80 on the container to whatever port you want on the host.

If it's clear enough to you and when you can get Nextcloud working, I'll close this.
Of course don't hesitate to tell me if I misunderstood.

@Sawn
Copy link
Author

Sawn commented Jun 29, 2016

Thank you for your fast answer.

You are right, I'm new to docker and misunderstood the requirements for the "backend" containers as I believed that I had to expose the port.

It's working now, sorry for disturbing and thanks again for your explanations.

I'll now look on how to switch memcaching to a linked redis container :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants