jwilder-nginx-proxy

With jwilder nginx-proxy, how to proxypass a subdirectory url to a specific container?

半城伤御伤魂 提交于 2019-12-04 08:47:31
I use jwilder/nginx-proxy to make a reverse proxy. I try to redirect http://localhost:8000/api to a specific php service. The directory structure: . +-- docker-compose.yml +-- nginx +-- nodejs | +-- index.js | +-- … +-- php | +-- api docker-compose.yml: version: "3.1" services: nginx-proxy: image: jwilder/nginx-proxy:alpine ports: - "8000:80" volumes: - ./php:/srv/www - /var/run/docker.sock:/tmp/docker.sock:ro nodejs: image: node:alpine environment: - NODE_ENV=production - VIRTUAL_HOST=localhost - VIRTUAL_PORT=8080 expose: - "8080" working_dir: /home/app restart: always volumes: - ./nodejs:

Docker nginx-proxy : proxy between containers

强颜欢笑 提交于 2019-12-01 05:32:18
问题 I am currently running a development stack using Docker-Compose in my company, to provide to developers everything they need to code our applications. It includes in particular: a Gitlab container (sameersbn/gitlab) to manage private GIT repositories, a Jenkins container (library/jenkins) for building and continuous integration, an Archiva container (ninjaben/archiva-docker) to manage Maven repositories. In order to secure the services through HTTPS, and exposing them to the outside world, I

How to join the default bridge network with docker-compose v2?

前提是你 提交于 2019-11-30 14:29:46
问题 I tried to setup an nginx-proxy container to access my other containers via subdomains on port 80 instead of special ports. As you can guess, I could not get it to work. I'm kind of new to docker itself and found that it's more comfortable for me to write docker-compose.yml files so I don't have to constantly write long docker run ... commands. I thought there's no difference in how you start the containers, either with docker or docker-compose . However, one difference I noticed is that

How to join the default bridge network with docker-compose v2?

谁说我不能喝 提交于 2019-11-30 10:52:37
I tried to setup an nginx-proxy container to access my other containers via subdomains on port 80 instead of special ports. As you can guess, I could not get it to work. I'm kind of new to docker itself and found that it's more comfortable for me to write docker-compose.yml files so I don't have to constantly write long docker run ... commands. I thought there's no difference in how you start the containers, either with docker or docker-compose . However, one difference I noticed is that starting the container with docker does not create any new networks, but with docker-compose there will be