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
Q1. Do you already have a WordPress setup that you want to continue with? [y/n]:
41
35
```
36
+
*Answer*
42
37
43
-
Frontend will be available on port [http://localhost:3000](http://localhost:3000)
44
-
45
-
### Evironment vars.
46
-
Create a `.env` file taking reference from `.env-example` inside frontend directory and add your WordPress Site URL ( for local development put `http://localhost:8020` as your WordPress URL)
38
+
`y`: If you would like to use this project's WordPress Docker setup ( In which case make sure to install and active all plugins from [backend/plugins-collection])
39
+
`n`: If you want to use your own WordPress setup.
47
40
48
-
## Development ( Developers only )
49
-
50
-
1. When we change the composer.json, run from root
51
-
```shell script
52
-
docker-compose -f backend/docker-compose.yml down && \
53
-
docker-compose -f backend/docker-compose.yml up -d
54
-
```
55
-
56
-
First line command will stops and removes all the docker containers and second line command will restart all containers.
57
-
Notice that `-d` is to run in detach mode and you can always remove that flag, and run the command so you can see the live logs.
58
-
Or you can check the logs for
59
-
60
-
2. Check the logs
61
-
While the above command is running in detached mode ( -d ), you can run this command in a new terminal tab to see the live logs.
62
-
```shell script
63
-
docker logs -f container-name
41
+
```bash
42
+
Q2. ✍️ What is your WP backend URL? (defaults to http://localhost:8020):
64
43
```
44
+
Leave it blank if you would like to use this project's WordPress Docker setup,
0 commit comments