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
Since database takes a brief moment for its setup, start with:
168
168
169
169
```bash
170
-
$ docker-compose up tilt_mariadb
170
+
$ dockercompose up tilt_mariadb
171
171
```
172
172
173
173
Then wait for MariaDB to accept incoming connections. Once this is done, you can stop `docker-compose` and start up everything with:
174
174
175
175
```bash
176
-
$ docker-compose up
176
+
$ dockercompose up
177
177
```
178
178
179
179
Depending on your setup, you might want to append the `-d` flag to run the containers in the background.
@@ -187,7 +187,7 @@ With everything up and running, you usually want to configure tilt. For this, yo
187
187
Since you have access to the server running tilt, you can spawn a shell in the tilt container and invoke the [usermod script](backend/src/usermod.ts). Please note that we're using `node:alpine` as a base image and therefore don't ship Bash. This script takes two arguments, the email of the user you want to change, as well as the group you want to assign to this user. To assign the `root` group to `you@example.com`, run:
@@ -271,21 +271,29 @@ If you found a bug or have an idea for a feature, simply [submit an issue](https
271
271
The tilt repository ships with a [docker-compose.yml](docker-compose.yml), which includes a sample setup with MariaDB, the test SMTP server [MailDev](https://github.com/maildev/maildev) and phpMyAdmin. To mimic the proxy'd setup, it also includes build instructions for a tilt container, as well as an NGINX container. You usually only need `db`, `phpmyadmin` and `maildev`, therefore it's sufficient to start them using:
272
272
273
273
```bash
274
-
$ docker-compose up db phpmyadmin maildev
274
+
dockercompose up db phpmyadmin maildev
275
275
```
276
276
277
-
For local development, the backend supports reading `.env` files. Refer to [`.env.example`](backend/.env.example) for such a configuration and match the ports from the Docker Compose configuration. You can then start the backend using:
277
+
For local development, the backend supports reading `.env` files. Refer to [`.env.example`](backend/.env.example) for such a configuration and match the ports from the Docker Compose configuration.
278
278
279
279
```bash
280
-
$ yarn backend::start
280
+
cp backend/.env.example backend/.env
281
281
```
282
282
283
-
As the frontend is built in modern React, we use [Webpack](https://webpack.js.org) and its devserver to develop. The backend runs on a different port, so we need to tell the frontend how to reach the backend. This can be done through the `API_BASE_URL` environment variable. To start the frontend devserver with the backend listening on port 3000, simply provide it using:
As the frontend is built in modern React, we use [Webpack](https://webpack.js.org) and its devserver to develop. The frontend is available at localhost:8080. The backend runs on a different port, so we need to tell the frontend how to reach the backend. This can be done through the `API_BASE_URL` environment variable. To start the frontend devserver with the backend listening on port 3000, simply provide it using:
0 commit comments