Skip to content

Commit 5f6fb97

Browse files
authored
Update README.md
1 parent 204fe97 commit 5f6fb97

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

README.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,7 @@ Unfortunately, docker-compose doesn't have any built in support for "singleton"
2626
My solution is to split up the above example into 3 projects and share the same network across all projects.
2727

2828
### router
29-
This is the web proxy (router). It sets up the nginx container, the jwilder nginx-gen container, and a letsencrypt companion.
30-
31-
By default it will also create a network called "router_default".
29+
This is the web proxy (router). It sets up the nginx container, the jwilder nginx-gen container, and a letsencrypt companion. By default it will also create a network called "router_default" (see caveat below).
3230

3331
### apps
3432
The only thing you have to change is to use the "router_default" network.
@@ -43,7 +41,7 @@ networks:
4341
## Usage
4442
To start everything up, just run `docker-compose up` for each project (starting with `router`). I have a helper script that does this (`up.sh`)
4543

46-
## Cavet
44+
## Caveat
4745
The network name is generated based on the router's project name (which is by default the directory name). If you rename the project then you have to rename the app networks.
4846

4947
An alternative solution would be to explicitly create your own network. For example:

0 commit comments

Comments
 (0)