You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| ui.docker | Included as fallback, if `SHARED_DOMAIN_SEGMENT` was left blank. |
135
-
| router.docker | Included as fallback, if `SHARED_DOMAIN_SEGMENT` was left blank. |
136
-
| pg-admin.docker | Included as fallback, if `SHARED_DOMAIN_SEGMENT` was left blank. |
137
-
|*.wod.docker | All subdomains under this wildcard. **Only one level of nesting **will work in most of the browsers****. |
138
-
|*.tpl.wod.docker | For default template, generated from [laravel-starter-tpl](https://github.com/wayofdev/laravel-starter-tpl)|
117
+
```bash
118
+
make env
119
+
```
139
120
140
-
<br>
121
+
Open this file and read the notes inside to make any necessary changes to fit your setup.
141
122
142
-
### → Finishing
123
+
6.**Install root certificate** and generate default project certs:
143
124
144
-
1. Install root certificate into systemand generate default certs:
125
+
This step installs the root certificate into your system's trust store and generates default SSL certificates for your local domains, which are listed in the `.env` file, under variable `TLS_DOMAINS`.
145
126
146
127
```bash
147
128
make cert-install
148
129
```
149
130
150
-
2. (Optional) Enable docker-compose.override file to run extra services, like pg-admin and others:
131
+
Currently, on macOS you may need to enter password several times to allow mkcert to install root certificate.
132
+
This is a one-time operation and details can be found in this upstream [issue](https://github.com/FiloSottile/mkcert/issues/415).
151
133
152
-
```bash
153
-
make override
154
-
```
134
+
7.**Run this project:**
155
135
156
-
3. Run this repository:
136
+
Start the Docker services defined in the repository.
157
137
158
138
```bash
159
139
make up
160
140
```
161
141
162
-
4.Check that everything works:
142
+
8.**Check that all Docker services are running:**
163
143
164
144
```bash
165
145
make ps
166
146
make logs
167
147
```
168
148
169
-
<br>
170
-
171
-
### → Outcome
149
+
9.**Ping `router.docker` to check if DNS is working:**
172
150
173
-
Services will be running under shared docker network, called `ss_shared_network` and all microservices, that will share same network, will be visible for Traefik, and local DNS, served by dnsmasq, will be available.
151
+
Ensure that the DNS setup is functioning correctly.
**Portrainer** — <https://ui.wod.docker> or <https://ui.docker>
159
+
Open [https://router.docker](https://router.docker)
180
160
181
-
**Pg-admin** (if `docker-compose.override.yaml` was enabled) — <https://pg-admin.wod.docker> or <https://pg-admin.docker>
161
+
At this point, you should have a working local development environment with DNS and SSL support for your projects.
182
162
183
163
<br>
184
164
185
-
## 🧪 Testing
186
-
187
-
You can check `Makefile` to get full list of commands for local testing. For testing, you can use these commands to test whole role or separate tasks:
188
-
189
-
Testing docker-compose using `dcgoss`:
165
+
## ⚡️ Connecting your Projects to Shared Services
166
+
167
+
To connect your projects to the shared services, configure your project's `docker-compose.yaml` file to connect to the shared network and Traefik.
168
+
169
+
For a quick example, you can check this [Laravel Starter Template](https://github.com/wayofdev/laravel-starter-tpl) repository's [docker-compose.yaml](https://github.com/wayofdev/laravel-starter-tpl/blob/develop/docker-compose.yaml) file, which includes a sample configuration for a Laravel project.
170
+
171
+
### → Sample Configuration
172
+
173
+
Your project should use the shared Docker network `network.ss` and Traefik labels to expose services to the outside world.
0 commit comments