Skip to content

Commit 8796eca

Browse files
authored
Update README.md
1 parent 711e85f commit 8796eca

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Diff for: README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ This service makes it easy to quickly setup an application where users can regis
4141
- Add the following service to your docker-compose.yml file:
4242
```yml
4343
authentication:
44-
image: mu-node-authentication-service
44+
image: aatauil/mu-node-authentication-service
4545
labels:
4646
- "logging=true"
4747
restart: always
@@ -114,14 +114,14 @@ This image uses the [mu-javascript-template](https://github.com/mu-semtech/mu-ja
114114
Quick example on how your docker-compose.yml file for this service will look like in development mode:
115115
```yml
116116
authentication:
117-
image: mu-node-authentication-service
117+
image: aatauil/mu-node-authentication-service
118118
ports:
119119
- 8888:80
120120
- 9229:9229
121121
environment:
122122
NODE_ENV: "development"
123123
links:
124-
- db:virtuoso
124+
- virtuoso:db
125125
volumes:
126126
- /path/to/local/cloned/mu-node-authentication-service/folder/:/app/
127127
labels:
@@ -136,7 +136,7 @@ Quick example on how your docker-compose.yml file for this service will look lik
136136
When using mu-authorization, you probably will want your requests to go through there first instead of straight to 'virtuoso'. In the yaml file above we see that 'db' is linked directly to 'virtuoso'. Change this to the name of the authorization service (e.g. database) if you need it to go through mu-authorization first.</sub>
137137
```
138138
links:
139-
- db:database
139+
- database:db
140140
```
141141
142142
---

0 commit comments

Comments
 (0)