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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+17-6Lines changed: 17 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,18 @@ Next start the Docker Compose stack that includes executor server with nessessar
76
76
docker compose up -d
77
77
```
78
78
79
-
You can now use `http://localhost:9800/v1/` endpoint to communicate with Open Runtimes Executor. You can see 'Getting Started' section of README to learn about endpoints.
79
+
For development with live reload, use Docker Compose watch which automatically syncs code changes to the container:
80
+
81
+
```bash
82
+
docker compose watch
83
+
```
84
+
85
+
The `docker-compose.override.yml` file configures the development environment:
86
+
- Changes to `app/` and `src/` sync and restart the container
87
+
- Changes to `tests/` and `phpunit.xml` sync without restart
88
+
- Changes to `composer.json` or `composer.lock` trigger a full rebuild
89
+
90
+
You can now use `http://localhost:9900/v1/` endpoint to communicate with Open Runtimes Executor. You can see 'Getting Started' section of README to learn about endpoints.
80
91
81
92
## Testing
82
93
@@ -97,19 +108,19 @@ To run tests, you need to start Docker Compose stack, and then run PHPUnit:
97
108
```bash
98
109
docker compose up -d
99
110
# Wait for ~5 seconds for executor to start
100
-
docker run --rm -v $PWD:/app --network executor_runtimes -w /app phpswoole/swoole:5.1.2-php8.3-alpine sh -c \ "composer test"
111
+
docker run --rm -v $PWD:/app --network executor_runtimes -w /app phpswoole/swoole:5.1.2-php8.3-alpine sh -c \ "composer test:e2e"
101
112
```
102
113
103
-
To run linter, you need to run Pint:
114
+
To format, you can run Pint with:
104
115
105
116
```bash
106
117
composer format
107
118
```
108
119
109
-
To run static code analysis, you need to run PHPStan:
120
+
To run static code analysis, you can run PHPStan with:
Searching for Open Runtimes, GitHub or StackOverflow and helping someone else who needs help. You can also help by teaching others how to contribute to Open Runtimes repo!
162
+
Searching for Open Runtimes, GitHub or StackOverflow and helping someone else who needs help. You can also help by teaching others how to contribute to Open Runtimes repo!
0 commit comments