|
24 | 24 | - To launch with ~node~ instead of ~nodemon~ simply prepend ~EXEC_MODE=node~ |
25 | 25 | to the ~docker-compose~ invocation |
26 | 26 | 6. The next steps will depend on the example in question |
27 | | - 1. Please refer to a tutorial's ~README.org~ (or video) |
| 27 | + 1. Please refer to a tutorial's ~README.md~ (or video) |
28 | 28 | 2. For many examples, changes in your local environment will be automatically |
29 | 29 | mapped into the docker container created via ~docker-compose~ |
30 | 30 | 1. For example, if you make changes within a tutorial's directory locally, |
31 | 31 | the container will automatically be restarted with those changes |
32 | 32 | * Errors |
33 | | -** The error is related to a tutorial's code/configs |
34 | | -1. Find the tutorial within the root directory of this repo |
35 | | -2. Submit a PR with the fix |
36 | | - 1. Make a comment above your fix with a brief description of the change |
37 | | - 2. Prepend ~FIXED-ERROR~ to this comment |
38 | | -3. Please do a global search of the repo to see other areas that might have this error |
39 | | - |
40 | 33 | ** The error is NOT related to a tutorial's code/configs |
41 | | -1. Find the tutorial within the root directory of this repo |
42 | | -2. Within the repo's ~readme.md~, find the slide in question |
| 34 | +1. Find the tutorial's directory within this repo |
| 35 | +2. Review ~readme.md~ and find the slide with the error |
43 | 36 | 3. Add a ~FIXED-ERROR~ bullet under the problematic text |
44 | 37 | - As a sub-bullet of ~FIXED-ERROR~, explain the correction |
| 38 | +4. Within the tutorial's ~readme.md~, update the ~Error Log~ section |
| 39 | +** The error is related to a tutorial's code/configs |
| 40 | +1. Find the tutorial's directory within this repo |
| 41 | +2. Find the erroneous file |
| 42 | +3. Submit a PR with the fix |
| 43 | + 1. Make a comment above your fix with a brief description of the change |
| 44 | + 2. Prepend ~FIXED-ERROR~ to this comment |
| 45 | +4. Within the tutorial's ~readme.md~, update the ~Error Log~ section |
| 46 | +5. Do a global search to find other areas that might have this error |
45 | 47 | * Additional Help |
46 | 48 | + Feel free to open an issue |
47 | 49 | * TOS |
|
0 commit comments